registry / @companion-ai/feynman / 0.5.30
@companion-ai/feynman@0.5.30
Research-first CLI agent built on Pi and alphaXiv
AI Security Review
scanned 26d ago · by lpm-firewall-aiSource inspection shows a version-gating preinstall check and an explicit initialization command that preserves existing files. The scanner signals do not establish malicious behavior in the inspected paths.
Static reason
One or more suspicious static signals were detected.
Trigger
The preinstall hook runs during installation; the project initialization writes run only when a user invokes `init`.
Impact
No confirmed attack surface was established in these behaviors.
Mechanism
The hook checks the Node version and exits if unsupported. The `init` command creates notes directories and adds project files only when those files are absent.
AI rationale
Source inspection shows a version-gating preinstall check and an explicit initialization command that preserves existing files. The scanner signals do not establish malicious behavior in the inspected paths.
Evidence
AGENTS.mdnotesnotes/session-logs/README.md
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The preinstall hook only runs a Node version check that exits when the runtime is unsupported.
- The project-file writes occur in the explicitly registered `init` command and target the current project directory.
- The CLI launcher checks peer availability, then loads the package CLI; its startup environment loading is limited to a cwd `.env` file.
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.30.
See all versions of @companion-ai/feynman for other recorded verdicts.
- Review the evidence and your use of @companion-ai/feynman@0.5.30 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.