@cityofzion/neon-js
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@cityofzion/neon-api | AI (dependencies): First-party monorepo dependency from CityOfZion org; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@cityofzion/neon-core | AI (dependencies): First-party monorepo dependency from CityOfZion org; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@cityofzion/neon-api | AI (phantom-deps): Umbrella re-export package; sibling dep declared but re-exported rather than directly imported — stable false positive. | ai | |
| phantom-deps | phantom-dep:@cityofzion/neon-nep5 | AI (phantom-deps): Same monorepo re-export pattern; stable false positive for this package. | ai |
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.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.