fraim@2.0.304
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest defines no install lifecycle hook, and the inspected source ties configuration changes to explicit FRAIM CLI setup with telemetry directed to a local receiver. The scanner's similarity labels do not establish malicious behavior in the reviewed source.
Decision evidence
public snapshot- package.json has no lifecycle scripts, and the entrypoints run the FRAIM CLI.
- Claude token telemetry is enabled during explicit setup and points to a localhost receiver; the local MCP server starts that receiver.
- IDE integration writes FRAIM-owned skills and commands, while project adapters target FRAIM-specific files.
- The reviewed Git, platform, installer, and scripts-check code performs package-related setup or checks.
- Diagnostics code redacts known secrets and FRAIM token patterns before displaying text.
- Project initialization can add Claude telemetry environment settings at the user level, affecting all Claude Code projects; the code preserves existing environment values and points telemetry to localhost.
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.304.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.304 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.