@kerno/cli@0.1.25
Kerno CLI - Local backend validation for AI-generated code, against your real stack.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource confirms a user-triggered unverified remote installer execution path, so the scanner's remote-execution finding is valid. It does not confirm malicious intent or unconsented install-time activity.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Run kerno init when the agent is absent, outdated, or forced to update.
Impact
A compromised remote installer could execute arbitrary code as the invoking user.
Mechanism
remote shell-script download and execution
AI rationale
Source confirms a user-triggered unverified remote installer execution path, so the scanner's remote-execution finding is valid. It does not confirm malicious intent or unconsented install-time activity.
Evidence
package.jsonpostinstall.cjscli.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
- cli.js fetches an agent install script from raw.githubusercontent.com and executes it with bash or PowerShell.
- The downloaded script is written to a temp install file and run without an in-package integrity check.
- PowerShell execution uses ExecutionPolicy Bypass on Windows.
- The remote installer is reached through the explicit kerno init flow.
Evidence against
- package.json postinstall runs only postinstall.cjs, which prints a banner.
- No install-time network, shell, credential harvesting, or agent-config mutation appears in postinstall.cjs.
- The remote URL is Kerno-owned, versioned (2026.8.7.2), and used for the documented first-party agent setup.
- CLI only prints Claude/Cursor MCP configuration; it does not write their config files.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemShell
HighEntropyStringsUrlStrings
Source & flagged code
12 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
318"use strict";
L319: if (process.env.NODE_ENV !== "production") {
L320: (function() {
...
L546: isMounted: ["isMounted", "Instead, make sure to clean up subscriptions and pending requests in componentWillUnmount to prevent memory leaks."],
L547: replaceState: ["replaceState", "Refactor your code to use setState instead (see https://github.com/facebook/react/issues/3236)."]
L548: };
...
L2023: var thenable = {
L2024: then: function(resolve4, reject) {
L2025: wasAwaited = true;
...
L2211: ];
L2212: if (process.platform !== "win32") {
L2213: module.exports.push(
Findings
4 Critical5 High5 Medium5 Low
CriticalCommand Output Exfiltrationcli.js
CriticalRemote Asset Decode Executecli.js
CriticalTrigger Reachable Dangerous Capabilitycli.js
CriticalPrevious Version Dangerous Deltacli.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processcli.js
HighShellcli.js
HighSame File Env Network Executioncli.js
HighSemantic Analysis Limitedcli.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumOversized Source Filecli.js
MediumOversized Cli Entrypoint
Affected versions and remediation
This report applies to @kerno/cli@0.1.25.
See all versions of @kerno/cli for other recorded verdicts.
- Review the evidence and your use of @kerno/cli@0.1.25 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.