@neon.id/jwt
2
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:jest | AI (typosquat): Scoped package @neon.id/jwt; Levenshtein match to jest is a false positive for this org's JWT library. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @neon.id/jwt; Levenshtein match to got is a false positive for this org's JWT library. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @neon.id/jwt; Levenshtein match to joi is a false positive for this org's JWT library. | ai |
v1.11.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.
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.