fraim@2.0.339
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe source confirms a conditional command injection vulnerability in the project initialization path. It warrants a warning, while the inspected source does not show an automatic install-time trigger or establish malicious intent.
Decision evidence
public snapshot- When project configuration is absent, `init-project` calls Git platform detection.
- The fallback builds a shell command using the first configured remote name without escaping it, creating a conditional command injection risk.
- The manifest exposes CLI entry points, and the risky path is reached through project initialization rather than an install hook.
- The inspected agent setup writes FRAIM-specific integration files; the diagnostic helper redacts FRAIM keys, and the session utility spawns commands with shell execution disabled.
- The injection path requires someone to run project initialization and reach the fallback remote lookup; it is not shown as an automatic install-time action.
- The inspected agent integrations and runtime operations do not establish a separate attack surface.
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.339.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.339 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.