registry / @companion-ai/feynman / 0.5.6
@companion-ai/feynman@0.5.6
Research-first CLI agent built on Pi and alphaXiv
AI Security Review
scanned 26d ago · by lpm-firewall-aiInspected source shows a version-only install hook and user-invoked project initialization with existence checks. The scanner’s dynamic loading and child-process signals correspond to launcher and helper behavior; no concrete attack behavior was found.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation runs the Node version check; a user can invoke the project init command.
Impact
No confirmed harmful effect; the observed file changes are limited to project initialization.
Mechanism
The init handler creates missing project notes and session-log directories and writes template files only when the target files do not already exist.
AI rationale
Inspected source shows a version-only install hook and user-invoked project initialization with existence checks. The scanner’s dynamic loading and child-process signals correspond to launcher and helper behavior; no concrete attack behavior was found.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The only install hook runs a Node version check; no install-time payload behavior is declared.
- Project file creation is part of the registered init command and targets AGENTS.md and session-log files under the project directory.
- The launcher loads the bundled CLI only after handling its version-only path.
- The bundled CLI starts its alpha helper as a child process using the current working directory and environment.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsTelemetryUrlStrings
WildcardDependency
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 High6 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
MediumWildcard Dependency
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
Affected versions and remediation
This report applies to @companion-ai/feynman@0.5.6.
See all versions of @companion-ai/feynman for other recorded verdicts.
- Review the evidence and your use of @companion-ai/feynman@0.5.6 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.