nostr-social-graph
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:cors | AI (phantom-deps): Framework-scoped dev dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/cors | AI (phantom-deps): TypeScript types for framework; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@msgpack/msgpack | AI (phantom-deps): Runtime dependency used indirectly in bundled code; stable for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.0.36 | 3 / 45 | |
| 1.0.33 | 2 / 37 | |
| 1.0.29 | 2 / 37 | |
| 1.0.28 | 2 / 37 | |
| 1.0.26 | 2 / 37 | |
| 1.0.25 | 2 / 37 |
v1.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.