@kerno/cli@0.1.29
Kerno CLI - Local backend validation for AI-generated code, against your real stack.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source establishes unverified remote code execution with inherited environment access, but it is explicitly user-invoked and not an install-time malicious chain. Downgrade to a warning rather than blocking publication.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user runs kerno init when the agent is absent, outdated, or forced to update.
Impact
A compromised remote installer could run arbitrary commands with the invoking user's permissions and access inherited environment values.
Mechanism
Remote shell-script download followed by local shell execution.
AI rationale
The source establishes unverified remote code execution with inherited environment access, but it is explicitly user-invoked and not an install-time malicious chain. Downgrade to a warning rather than blocking publication.
Evidence
cli.js.kerno
Network endpoints1
raw.githubusercontent.com/kernoio/kerno-agent-runtimes/${config.AGENT_VERSION}/install.${this.shellExtension}
Decision evidence
public snapshotAI called this Suspicious at 95.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The explicit init command starts an agent.
- Init downloads a shell script from raw GitHub and executes it without an integrity check.
- The downloaded script inherits the full process environment.
Evidence against
- The npm postinstall script only reads its package version and prints a banner.
- Remote script execution is reached through the user-invoked init command, not automatically during installation.
- The CLI prints MCP setup instructions rather than automatically changing Claude Code or Cursor settings.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
NoLicense
Oversized source lightweight scan
cli.js
Source & flagged code
11 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
3 Critical5 High5 Medium5 Low
CriticalRemote Asset Decode Executecli.js
CriticalTrigger Reachable Dangerous Capabilitycli.js
CriticalPrevious Version Dangerous Deltacli.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
Medium
Affected versions and remediation
This report applies to @kerno/cli@0.1.29.
See all versions of @kerno/cli for other recorded verdicts.
- Review the evidence and your use of @kerno/cli@0.1.29 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.