fraim@2.0.305
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found setup-triggered local token metrics and FRAIM-owned agent files, with no npm lifecycle hook or concrete attack behavior. The scanner’s similarity labels did not establish malicious behavior in the inspected source.
Decision evidence
public snapshot- The manifest and entrypoints route users into the FRAIM CLI; no npm lifecycle hook was found.
- Claude token metrics are enabled through the add-ide or init-project setup paths and sent to a loopback receiver.
- Agent integration writes FRAIM-owned skills and commands during setup; project adapter writes are restricted to the project root.
- Flagged diagnostic, git, marketplace, cookie, installer and connectivity code inspected as product functionality; no concrete attack behavior identified.
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.305.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.305 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.