@companion-ai/feynman@0.5.57
The open source AI research agent.
AI Security Review
scanned 12d ago · by lpm-firewall-aiStatic inspection found no malicious install hook or credential theft. The default-on telemetry path can transmit failed tool-result text, creating a conditional privacy risk that supports a warning rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
A CLI-launched Pi session runs a tool that reports an error while telemetry is enabled.
Impact
Sensitive text included in a tool error may be disclosed to the telemetry collector.
Mechanism
The extension extracts text content from the failed result and adds it to a captured telemetry event.
AI rationale
Static inspection found no malicious install hook or credential theft. The default-on telemetry path can transmit failed tool-result text, creating a conditional privacy risk that supports a warning rather than a block.
Evidence
dist/cli.jsdist/pi/runtime.jsdist/telemetry/posthog.jsextensions/research-tools/telemetry.tsextensions/research-tools.ts
Network endpoints1
us.i.posthog.com
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The preinstall hook runs a Node version check that exits on unsupported versions.
- The explicit init command creates AGENTS.md only when that file is absent.
- CLI startup initializes telemetry and passes its settings to the Pi child; the first-run notice describes error telemetry generally.
- Telemetry can be disabled through environment settings, and its default collector is Feynman's PostHog host.
- When a Pi tool reports an error, the extension extracts text from its result and includes it in a telemetry event sent to the configured collector.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsTelemetryUrlStrings
Source & flagged code
5 flaggedpackage.jsonView file
•scripts.preinstall = node ./scripts/check-node-version.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgbin/feynman.jsView file
23if (compareNodeVersions(parseNodeVersion(process.versions.node), parseNodeVersion(MIN_NODE_VERSION)) < 0) {
L24: const isWindows = process.platform === "win32";
L25: console.error(`feynman requires Node.js ${MIN_NODE_VERSION} or newer (detected ${process.versions.node}).`);
L26: console.error(isWindows
L27: ? "Install a supported Node.js release from https://nodejs.org, or use the standalone installer:"
L28: : `Switch to a supported Node release with \`nvm install ${PREFERRED_NODE_MAJOR} && nvm use ${PREFERRED_NODE_MAJOR}\`, or use the standalone installer:`);
...
L35:
L36: // `--version` needs only package.json; answer it without loading the CLI.
L37: if (process.argv.length === 3 && (process.argv[2] === "--version" || process.argv[2] === "-v")) {
L38: const { readFileSync } = await
High
Sandbox Evasion Gated Capability
Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
bin/feynman.jsView on unpkg · L23Findings
3 High5 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSandbox Evasion Gated Capabilitybin/feynman.js
HighSemantic Analysis Limiteddist/cli.js#virtual:normalized:round1
MediumDynamic Requirebin/feynman.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/install/install-skills.sh
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
Affected versions and remediation
This report applies to @companion-ai/feynman@0.5.57.
See all versions of @companion-ai/feynman for other recorded verdicts.
- Review the evidence and your use of @companion-ai/feynman@0.5.57 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.