registry / @kerno/cli / 0.2.2
@kerno/cli@0.2.2
Kerno CLI - Local backend validation for AI-generated code, against your real stack.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe automatic lifecycle hook is display-only, while the executable's inspected MCP setup targets localhost. Static inspection found no concrete malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Package installation runs the banner hook; user execution runs the CLI.
Impact
No unconsented persistence, foreign agent-control mutation, credential exposure, or destructive effect was established.
Mechanism
The hook writes display text to the terminal. The CLI produces local MCP connection configuration.
AI rationale
The automatic lifecycle hook is display-only, while the executable's inspected MCP setup targets localhost. Static inspection found no concrete malicious behavior.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes cli.js as its command-line entrypoint and names postinstall.cjs as its only install hook.
- The install hook only assembles and prints a terminal banner.
- The CLI constructs MCP configuration for a localhost endpoint rather than writing an external agent configuration.
- No credential harvesting, remote payload execution, destructive action, or install-time file mutation was found in the inspected sources.
Evidence against
- Running the CLI initializes usage telemetry and records an installation event.
Behavioral surface
EnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
NoLicense
Oversized source lightweight scan
cli.js4.65 MB file, sampled 256 KB
Source & flagged code
9 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 Critical4 High5 Medium5 Low
CriticalRemote Asset Decode Executecli.js
CriticalTrigger Reachable Dangerous Capabilitycli.js
HighInstall Time Lifecycle Scriptspackage.json
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
LowFilesystem
Low
Affected versions and remediation
This report applies to @kerno/cli@0.2.2.
See all versions of @kerno/cli for other recorded verdicts.
- Review the evidence and your use of @kerno/cli@0.2.2 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.