@kerno/cli@0.1.26
Kerno CLI - Local backend validation for AI-generated code, against your real stack.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe postinstall hook is benign, while the CLI intentionally provides an unsigned remote installer. Treat this as a dangerous unresolved capability requiring a warning, not confirmed malware.
Decision evidence
public snapshot- cli.js downloads a GitHub install script and runs it with bash or PowerShell.
- The downloaded script has no visible checksum/signature verification.
- The spawned installer inherits process.env.
- Remote execution is reachable through explicit `kerno init` when the agent is absent or updated.
- postinstall.cjs only prints an install banner.
- Remote installer URL is pinned to embedded agent version 2026.8.10.
- MCP configuration is displayed for the user; no foreign agent config is written.
- No source-confirmed credential harvesting or destructive behavior was found.
Source & flagged code
11 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.26.
See all versions of @kerno/cli for other recorded verdicts.
- Review the evidence and your use of @kerno/cli@0.1.26 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.