fraim@2.0.297
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found user-triggered setup for FRAIM-owned agent integrations, which changes agent configuration and warrants a warning. The inspected source does not establish a concrete malicious action or an automatic npm install-time mutation.
Decision evidence
public snapshot- The package exposes CLI entrypoints, and the inspected manifest excerpt does not show an install hook.
- The setup code writes FRAIM-specific Claude skill and command files under the user's Claude configuration.
- The adapter paths are named for FRAIM-specific project files, including Cursor, Claude, and Codex.
- The user-level sync path refreshes integration artifacts when the user runs the global sync command.
- First-run setup also installs global rules; this is agent integration setup with a user-level configuration effect.
- The inspected sources show no confirmed credential theft, destructive behavior, or remote code execution.
- The flagged Claude integration files are FRAIM-specific, and global sync is tied to a user-invoked command.
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.297.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.297 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.