fraim@2.0.277
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found no lifecycle hook or concrete attack behavior. The flagged telemetry and agent setup is reachable through CLI setup commands and uses a localhost metrics receiver or FRAIM-managed files.
Decision evidence
public snapshot- package.json declares CLI entrypoints and dependencies but no lifecycle script; execution starts through the CLI.
- Claude telemetry settings are written by explicit project setup or IDE-add commands and direct metrics to the local receiver.
- Agent integration writes FRAIM-named files into existing agent directories or project paths; no unconsented install-time control-surface mutation was identified.
- The diagnostics excerpt sanitizes FRAIM tokens; reviewed source did not establish credential theft, destructive behavior, or another attack.
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.277.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.277 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.