fraim@2.0.306
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest has no install hook, and the flagged agent configuration behavior is tied to explicit setup commands with a localhost metrics endpoint. The inspected files support normal CLI, setup, diagnostic, and product functions; scanner similarity labels alone do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines the CLI entrypoints and has no install lifecycle hook.
- Claude telemetry settings are written by a setup helper; its configured OTLP endpoint is localhost.
- The telemetry helper is called from the add-ide and init-project commands.
- Agent integration files install FRAIM-specific invocation artifacts or merge a marked FRAIM section into existing content.
- The diagnostic helper sanitizes known secrets in text it processes.
- The remaining inspected files concern CLI startup, project setup, Git or marketplace utilities, installer templates, cookies, and connectivity checks; no concrete attack behavior was identified.
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.306.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.306 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.