fraim@2.0.287
FRAIM core CLI and MCP package.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis package has no install lifecycle hook, so the behavior is not an unconsented install-time compromise. Its explicit sync flow still downloads opaque remote scripts and modifies multiple AI-agent control surfaces, which warrants a warning.
Decision evidence
public snapshot- The user-invoked sync command downloads a registry payload from the configured FRAIM server.
- Sync writes remotely supplied files into the user's FRAIM scripts directory without validating their contents.
- Sync creates a user-level package manifest and runs npm install for a runtime dependency.
- Sync updates global Claude, Cursor, Codex, Grok, Gemini, Windsurf, and Kiro agent invocation files when their directories exist.
- package.json has no preinstall, install, or postinstall hook.
- The entrypoints only register and run the CLI after an explicit command.
- The agent-control writes are reached through explicit setup or sync actions, not package installation.
Source & flagged code
11 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.287.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.287 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.