registry / @kerno/cli / 1.1.3
@kerno/cli@1.1.3
Kerno CLI - Local runtime backend testing inside your coding agent's loop.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged install hook only prints a welcome banner. The remote installer is part of the agent setup flow, and audit data sharing is presented to the user with a separate choice for sending code extracts to the judge.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The postinstall hook runs during installation; audit uploads and agent installation are reached through CLI workflows.
Impact
No malicious behavior was found. Audit data sharing is disclosed, and the install hook performs no network action.
Mechanism
The hook prints a welcome banner. Audit sharing is presented to the user, while agent setup fetches an installer from Kerno’s agent-runtimes repository.
AI rationale
The flagged install hook only prints a welcome banner. The remote installer is part of the agent setup flow, and audit data sharing is presented to the user with a separate choice for sending code extracts to the judge.
Evidence
/dev/ttyOS temporary directory/install.<shellExtension>
Network endpoints4
api.kerno.ioproxy.kerno.ioeu.i.posthog.comraw.githubusercontent.com
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes cli.js as the kerno command-line entry point.
- The postinstall hook prints a banner to /dev/tty or stderr.
- The CLI asks whether to send the finished audit run to Kerno and says the choice can be changed later.
- The CLI separately asks permission for the judge to read code extracts.
- Audit usage events are sent only when the saved sharing choice enables uploads.
- The agent installer fetches its install script from Kerno’s agent-runtimes repository.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemShell
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 path23 = __require("path");
...
L990: this._outputConfiguration = {
L991: writeOut: (str) => process15.stdout.write(str),
L992: writeErr: (str) => process15.stderr.write(str),
Critical
Findings
2 Critical6 High5 Medium5 Low
CriticalRemote Asset Decode Executecli.js
CriticalTrigger Reachable Dangerous Capabilitycli.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processcli.js
HighShellcli.js
HighCredential Redirect Persistencecli.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
Affected versions and remediation
This report applies to @kerno/cli@1.1.3.
See all versions of @kerno/cli for other recorded verdicts.
- Review the evidence and your use of @kerno/cli@1.1.3 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.