fraim@2.0.344
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package has no install lifecycle hooks, and the flagged sources inspected support normal CLI and local product functions. Setup enables token metrics through user-invoked commands; the inspected receiver handles token usage locally, so the static similarity and telemetry signals do not establish malicious behavior.
Decision evidence
public snapshot- package.json has no lifecycle scripts; inspected entrypoints and flagged modules show CLI, project, registry, and local utility behavior, with no confirmed attack.
- Claude token telemetry is enabled by explicit setup commands and writes settings for local collection; the receiver parses token usage metrics and serves snapshots over localhost.
Source & flagged code
16 flagged · loading sourcePackage source references child process execution.
dist/src/core/utils/git-utils.jsView on unpkg · L9Package source references shell execution.
dist/src/cli/doctor/checks/scripts-checks.jsView on unpkg · L235Findings
Affected versions and remediation
This report applies to fraim@2.0.344.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.344 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.