fraim@2.0.303
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest declares CLI entrypoints without npm lifecycle scripts or a runtime self-dependency. The inspected settings changes are activated by setup commands and direct token metrics to a loopback receiver; source inspection did not establish malicious behavior.
Decision evidence
public snapshot- package.json exposes CLI entrypoints and contains no lifecycle scripts or runtime dependency on fraim.
- Claude Code setup adds missing token-metrics settings pointed at a loopback receiver; explicit CLI setup commands activate the helper.
- Agent setup installs FRAIM-specific files, and the project adapter helper confines writes to the project root.
- The diagnostics helper redacts known secrets and FRAIM tokens from returned text.
- The other inspected paths implement CLI, repository, marketplace, cookie, installer, and connectivity functions; they did not establish an attack.
Source & flagged code
17 flagged · loading sourcePackage source references child process execution.
dist/src/core/utils/git-utils.jsView on unpkg · L9Package source references dynamic require/import behavior.
bin/fraim.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to fraim@2.0.303.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.303 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.