fraim@2.0.320
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe inspected source confirms a reachable shell injection path in project setup, contingent on a crafted Git remote configuration. This is a serious vulnerability, but the inspected behavior does not establish package malware or an install-time attack.
Decision evidence
public snapshot- When the project config is absent, `init-project` calls Git platform detection.
- If the `origin` lookup fails, the helper uses the first remote name in a command passed to `execSync`; shell syntax in a crafted name can execute during setup.
- The diagnostic location reads and redacts local text; it does not establish a separate external receiver.
- The vulnerable path requires a user to run project setup with a crafted Git remote configuration; this supports a vulnerability warning rather than a finding of package malware.
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.320.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.320 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.