@cityofzion/neon-api
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.10.1 | 0 / 0 | |
| 5.10.0 | 0 / 0 | |
| 5.9.0 | 0 / 0 | |
| 5.8.1 | 0 / 0 | |
| 5.8.0 | 0 / 0 | |
| 5.7.0 | 0 / 0 |
v5.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lllwvlvwlll) than the most recent previously approved version (snowypowers) on 2026-07-15, but lllwvlvwlll is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.