@leanandmean/coding-agent@0.74.1-scramjet.56
Coding agent CLI with read, bash, edit, write tools and session management
AI Security Review
scanned 1mo ago · by lpm-firewall-aiLifecycle metadata contains only ordinary build and test scripts, and the shell helpers match a coding agent the user runs. Example theme, notify, GitHub, Doom, and highlighter files do not add an automatic attack chain.
Decision evidence
public snapshot- package.json has no preinstall, install, or postinstall scripts and no bin entry; scripts are only clean, dev, build, copy-assets, and test.
- dist/core/exec.js and dist/utils/shell.js spawn a caller-supplied command or the resolved user shell only when the coding-agent runtime invokes them.
- Optional examples query macOS appearance, write terminal notifications, or list open GitHub issues with gh; doom.js is an example module and highlight.min.js is the export HTML highlighter.
- The CLI product includes shell execution, so child_process use is expected once a user runs the agent or loads an example extension.
- No install-time hook, self-dependency lifecycle chain, hidden credential send, or foreign agent-config write was found.
Source & flagged code
11 flaggedPackage source references shell execution.
examples/extensions/mac-system-theme.tsView on unpkg · L11Findings
Affected versions and remediation
This report applies to @leanandmean/coding-agent@0.74.1-scramjet.56.
See all versions of @leanandmean/coding-agent for other recorded verdicts.
- Review the evidence and your use of @leanandmean/coding-agent@0.74.1-scramjet.56 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.