@kerno/cli@1.0.0
Kerno CLI - Local backend validation for AI-generated code, against your real stack.
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe scanner’s execution and network indicators correspond to the user-invoked Kerno agent setup flow, while the install hook only prints a banner. The inspected telemetry is directed to the configured first-party analytics endpoint, and no concrete malicious behavior was found.
Decision evidence
public snapshot- The postinstall hook runs postinstall.cjs, which only prints a banner to the terminal.
- The CLI’s init flow downloads the Kerno agent installer when the agent needs installation or updating.
- The installer comes from Kerno’s kerno-agent-runtimes repository at a configured version; the CLI runs it as a shell or PowerShell script during agent setup.
- Installer failure output is sent as a diagnostic event to the configured first-party PostHog endpoint.
- The inspected source shows no malicious behavior beyond these package-aligned setup and telemetry functions.
- The CLI executes a downloaded installer, and on failure includes its recent output in telemetry.
- The CLI initializes analytics during startup and identifies logged-in users.
Source & flagged code
9 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @kerno/cli@1.0.0.
See all versions of @kerno/cli for other recorded verdicts.
- Review the evidence and your use of @kerno/cli@1.0.0 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.