@neon.id/cli
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
bianpratama
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @neon.id/cli is a scoped CLI tool with no relation to joi; Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:vercel | AI (phantom-deps): CLI wrapper invokes vercel via execa, not import; phantom-dep is a stable false positive. | ai | |
| phantom-deps | phantom-dep:wrangler | AI (phantom-deps): CLI wrapper invokes wrangler via execa, not import; phantom-dep is a stable false positive. | ai | |
| phantom-deps | phantom-dep:chromatic | AI (phantom-deps): CLI wrapper invokes chromatic via execa, not import; phantom-dep is a stable false positive. | ai | |
| phantom-deps | phantom-dep:pathe | AI (phantom-deps): Likely used in build/config scripts rather than direct import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Likely used in build/config scripts; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:js-base64 | AI (phantom-deps): Stable false positive; used in config/build context not direct import. | ai | |
| phantom-deps | phantom-dep:tsc-alias | AI (phantom-deps): Build tool invoked via CLI, not imported; stable false positive. | ai | |
| phantom-deps | phantom-dep:@clack/prompts | AI (phantom-deps): Prompts library likely used in bundled output; stable false positive for this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.24.0 | 24 / 16 |
v0.24.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.