@kerno/cli@0.2.0
Kerno CLI - Local backend validation for AI-generated code, against your real stack.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package contains a concrete remote-code execution path, but it is user-invoked rather than an install-time hook and the reviewed source does not establish malicious intent or data theft.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running kerno init when the agent must be installed or updated.
Impact
A changed remote installer could execute arbitrary commands with the invoking user's privileges.
Mechanism
Downloads a GitHub-hosted installer and runs it with Bash or PowerShell.
AI rationale
The package contains a concrete remote-code execution path, but it is user-invoked rather than an install-time hook and the reviewed source does not establish malicious intent or data theft.
Evidence
cli.js
Network endpoints1
raw.githubusercontent.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The init flow downloads an external shell or PowerShell installer from GitHub and executes it locally.
- The downloaded installer is not included in the package or integrity-verified before execution.
- The remote installer inherits the caller's environment.
Evidence against
- The npm postinstall hook only prints a banner and does not download or execute code.
- Remote installer execution is reached from the user-invoked init flow, not automatically during npm installation.
- No package source evidence shows secret harvesting or exfiltration by the CLI itself.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
NoLicense
Oversized source lightweight scan
Source & flagged code
10 flaggedpackage.jsonView file
•scripts.postinstall = node postinstall.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node postinstall.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgcli.jsView file
48* Constructs the CommanderError class
L49: * @param {number} exitCode suggested exit code which could be used with process.exit
L50: * @param {string} code an id string representing the error
...
L128: /**
L129: * @api private
L130: */
...
L941: var EventEmitter5 = __require("events").EventEmitter;
L942: var childProcess = __require("child_process");
L943: var path16 = __require("path");
...
L990: this._outputConfiguration = {
L991: writeOut: (str) => process15.stdout.write(str),
L992: writeErr: (str) => process15.stderr.write(str),
Critical
Findings
2 Critical5 High5 Medium5 Low
CriticalRemote Asset Decode Executecli.js
CriticalTrigger Reachable Dangerous Capabilitycli.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processcli.js
HighSame File Env Network Executioncli.js
HighCommand Output Exfiltrationcli.js
HighSemantic Analysis Limitedcli.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumOversized Source Filecli.js
MediumOversized Cli Entrypointcli.js
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to @kerno/cli@0.2.0.
See all versions of @kerno/cli for other recorded verdicts.
- Review the evidence and your use of @kerno/cli@0.2.0 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.