fraim@2.0.313
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and the inspected configuration changes are reached through explicit CLI operations. Source review found no concrete attack behavior corroborating the scanner’s similarity labels.
Decision evidence
public snapshot- package.json identifies the CLI entrypoints; the inspected manifest has no lifecycle scripts.
- Claude token metrics and agent configuration are set up by CLI commands, and the telemetry endpoint is local.
- The agent adapter paths and user-level sync support FRAIM configuration setup.
- The diagnostics helper masks secret-like values; the other inspected files handle CLI, Git, workflow, installer, marketplace, cookie, and connectivity functions.
- Static similarity labels were not corroborated by inspected source behavior showing an attack.
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.313.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.313 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.