@kerno/cli@0.1.24
Kerno CLI - Local backend validation for AI-generated code, against your real stack.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a concrete remote-code-execution supply-chain risk, but source confines it to an explicit first-party agent setup command and does not show malicious install-time behavior or foreign AI-agent configuration mutation.
Decision evidence
public snapshot- cli.js downloads a shell/PowerShell installer from raw.githubusercontent.com.
- cli.js writes the response to a temp script and executes it with bash or PowerShell.
- No hash, signature, or other integrity verification precedes execution.
- package.json postinstall only invokes postinstall.cjs.
- postinstall.cjs only reads package.json and prints a banner.
- Remote installer execution is reached through explicit kerno init/agent setup, not install time.
- MCP integration is displayed as instructions; no Claude/Cursor config is written.
Source & flagged code
12 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @kerno/cli@0.1.24.
See all versions of @kerno/cli for other recorded verdicts.
- Review the evidence and your use of @kerno/cli@0.1.24 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.