fraim@2.0.319
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection did not verify the scanner’s similarity labels as attack behavior. The reviewed agent configuration changes are tied to invoked setup features and FRAIM-specific artifacts, and the source does not establish a concrete attack.
Decision evidence
public snapshot- package.json names the CLI entrypoints; no lifecycle command is declared in the inspected manifest.
- Claude telemetry writes settings only when the setup helper is called, and adds values only for keys the user has not set.
- IDE setup installs FRAIM discovery files only when the corresponding IDE configuration directory exists.
- Project agent adapters use FRAIM-specific paths and managed-section markers.
- The inspected runtime paths perform CLI dispatch, diagnostics, Git or workflow setup, installer rendering, cookie handling, and marketplace validation; they do not establish an attack.
- No inspected source establishes credential theft, unconsented lifecycle mutation, or another concrete 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.319.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.319 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.