fraim@2.0.281
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe scanner similarity labels are not proof of malicious behavior. Source inspection found no package lifecycle hook or concrete attack; the flagged settings changes are part of explicit FRAIM setup and route token metrics to a local receiver.
Decision evidence
public snapshot- package.json exposes the CLI entrypoints and ends after dependencies without a lifecycle script.
- The Claude setup commands enable token metrics through an OTLP endpoint on localhost and merge the settings without replacing existing environment values.
- Agent integration helpers install FRAIM-specific artifacts during setup; inspected project writes are constrained to the project root.
- The flagged runtime paths implement CLI commands, diagnostics, local configuration checks, and scoped repository helpers; inspection found no concrete attack behavior.
Source & flagged code
19 flagged · loading sourcePackage source references child process execution.
dist/src/core/utils/git-utils.jsView on unpkg · L9Package source references shell execution.
dist/src/cli/doctor/checks/scripts-checks.jsView on unpkg · L170Findings
Affected versions and remediation
This report applies to fraim@2.0.281.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.281 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.