@kerno/cli@1.1.1
Kerno CLI - Local runtime backend testing inside your coding agent's loop.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe audit feature defaults to uploading reports with evidence, while headless runs bypass the sharing disclosure. This is a real consent and data-sharing risk, but the upload is part of the package’s audit service and requires a Kerno login, so the evidence supports a warning rather than a block.
Decision evidence
public snapshot- Audit sharing defaults to uploading runs with evidence enabled.
- The disclosure gate skips the sharing prompt when no terminal is available.
- The audit flow uploads its report to the Kerno backend and includes evidence when enabled.
- The postinstall hook prints a welcome banner.
- Uploading requires the audit flow to have a valid Kerno login token and organization.
- The package’s stated purpose is local backend validation, and the upload belongs to its audit feature.
Source & flagged code
12 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.1.1.
See all versions of @kerno/cli for other recorded verdicts.
- Review the evidence and your use of @kerno/cli@1.1.1 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.