@kerno/cli@0.1.27
Kerno CLI - Local backend validation for AI-generated code, against your real stack.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiNo unconsented install-time execution or foreign AI-agent configuration mutation was found. The explicit remote installer execution is a meaningful supply-chain risk but is package-aligned and user-invoked.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
User runs `kerno init` when the agent is absent or requires updating.
Impact
A compromised or substituted GitHub-hosted installer could execute with the invoking user's privileges.
Mechanism
downloaded shell/PowerShell installer is written to a temp file and spawned
AI rationale
No unconsented install-time execution or foreign AI-agent configuration mutation was found. The explicit remote installer execution is a meaningful supply-chain risk but is package-aligned and user-invoked.
Evidence
package.jsonpostinstall.cjscli.js~/.kerno/assets/agent/2026.8.12temporary install.sh or install.ps1
Network endpoints2
raw.githubusercontent.com/kernoio/kerno-agent-runtimes/2026.8.12/install.shraw.githubusercontent.com/kernoio/kerno-agent-runtimes/2026.8.12/install.ps1
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- `kerno init` downloads a remote installer then executes it with bash or PowerShell.
- The remote installer is fetched from GitHub without an integrity check before execution.
Evidence against
- The npm postinstall hook only prints a banner; it does not download or execute payloads.
- Remote installation is reached from the explicit `init` command, not during npm installation.
- The installer URL is package/vendor-aligned and versioned.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemShell
HighEntropyStringsUrlStrings
NoLicense
Oversized source lightweight scan
cli.js4.20 MB file, sampled 256 KB
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
2 Critical7 High5 Medium5 Low
CriticalRemote Asset Decode Executecli.js
CriticalTrigger Reachable Dangerous Capabilitycli.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processcli.js
HighShellcli.js
HighSame File Env Network Executioncli.js
HighEntrypoint Foreign Package Code Overwritecli.js
HighCommand Output Exfiltrationcli.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.27.
See all versions of @kerno/cli for other recorded verdicts.
- Review the evidence and your use of @kerno/cli@0.1.27 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.