registry / @companion-ai/feynman / 0.5.15
@companion-ai/feynman@0.5.15
Research-first CLI agent built on Pi and alphaXiv
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe inspected lifecycle hook is a Node version check, and the flagged project configuration behavior is scoped to an explicitly invoked init command that preserves an existing AGENTS.md. The scanner hints do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation invokes the Node version check; the project init behavior requires a user to invoke the init command.
Impact
The inspected behavior does not establish unauthorized changes, credential exposure, or execution of a remote payload.
Mechanism
The preinstall hook checks the Node version. The init command creates project notes and an AGENTS.md file only if that file is absent.
AI rationale
The inspected lifecycle hook is a Node version check, and the flagged project configuration behavior is scoped to an explicitly invoked init command that preserves an existing AGENTS.md. The scanner hints do not establish malicious behavior.
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The preinstall hook only runs a Node version check; no install-time project mutation is indicated.
- The launcher loads the CLI after its version check, and its --version path exits without loading the CLI.
- The project init command targets the current project and creates AGENTS.md only when it is absent.
- The CLI loads a working-directory .env file; this source excerpt shows no credential forwarding or exfiltration.
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") {
L38: const { readFileSync } = await import("node:fs");
L39: conso
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.15.
See all versions of @companion-ai/feynman for other recorded verdicts.
- Review the evidence and your use of @companion-ai/feynman@0.5.15 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.