Setups

n8n: our probe ran the wrong package manager

Not a finding about n8n. On 2026-09-13 our probe ran npm; this project declares pnpm 12.3.4, and npm could not resolve its workspace: dependencies.

About n8n

This receipt is about our tooling, not about n8n. The project's package.json declares packageManager: pnpm@12.3.4 and engines.pnpm: >=12.3.4. Our probe ran npm install anyway, and npm cannot resolve the workspace: protocol pnpm uses, so it exited 1. We read that same package.json to publish this listing's Node version floor, so the instruction was in our hands and we did not act on it. Nothing here says whether n8n's dependencies resolve; we did not find out.

npm install --ignore-scripts --no-audit --no-fund --no-update-notifier exited 1 after 15 seconds. It said: code EUNSUPPORTEDPROTOCOL, Unsupported URL Type "workspace:": workspace:*.

We cloned the repository at commit 4169b55bf3b3 and ran it under sandbox-exec -- (deny default) after importing the base BSD profile, reads allowed only under the system and toolchain paths and the scratch directory, writes confined to that scratch directory, the environment replaced with env -i, and lifecycle scripts disabled. The user's home directory is on no allow list. Node v26.7.0, npm 11.19.0. We did not run the bot: this is an observation about whether its dependencies resolve on that day, on that toolchain, and nothing more.

Source