@neon.id/sql
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:qs | AI (typosquat): Scoped @neon.id/sql is clearly not a typosquat of 'qs'; Levenshtein match is spurious for scoped packages. | ai | |
| phantom-deps | phantom-dep:fflate | AI (phantom-deps): fflate is a declared dependency used in build/config context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:pkg-types | AI (phantom-deps): pkg-types is a declared dependency used in build/config context; stable false positive for this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 20 / 14 |
v0.12.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.