fraim@2.0.309
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest has no lifecycle hooks, and the inspected configuration changes are tied to setup flows and FRAIM-specific artifacts. The flagged runtime paths show local diagnostics and ordinary connectivity checks; no concrete attack behavior was identified.
Decision evidence
public snapshot- package.json has no lifecycle scripts, and its dependency object closes without another package hook.
- Claude Code telemetry is added by an explicit setup helper, preserves existing values, and points metrics to a local receiver; the integration helper writes FRAIM-specific files.
- The agent adapter paths are FRAIM-specific, and the override command requires explicit options and validates the requested path.
- The diagnostics helper redacts known secrets and FRAIM tokens; the connectivity module is a doctor check.
- The inspected git utilities restrict repository URL schemes, and the CLI entrypoint loads the compiled CLI.
- The first-run installer is invoked from its onboarding flow; user-level setup and managed Node paths are rooted in FRAIM directories.
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.309.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.309 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.