fraim@2.0.311
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the reviewed source ties agent configuration changes to CLI setup operations. The flagged code showed FRAIM-specific setup and diagnostic behavior; source inspection did not establish a concrete attack.
Decision evidence
public snapshot- The manifest declares the CLI entrypoints and ends with ordinary dependencies; it has no lifecycle hook.
- Claude telemetry settings are handled by a helper that merges missing environment values into the user’s Claude settings; the indicated range shows that it reads that settings file.
- Global Claude invocation files are installed only when the Claude directory exists, and FRAIM adapter files use FRAIM-specific paths.
- The MCP diagnostics helper redacts known secrets and FRAIM tokens; the git utility accepts explicit local repository paths.
- The override command validates a user-supplied relative path; first-run code imports setup helpers as part of CLI operation.
- Other reviewed paths handle user-level dependencies, CLI dispatch, customer repository snapshots, workflow files, platform detection, installer page templates, marketplace validation, session cookies, and MCP connectivity checks.
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.311.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.311 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.