@tpluscode/rdf-ns-builders
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
tpluscode
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/rdfjs__namespace | AI (phantom-deps): TypeScript type definition package; loaded by convention, not direct import. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@zazuko/prefixes | AI (phantom-deps): Used in generated vocabulary files and config; indirect usage pattern is expected for this generated namespace builder package. | ai | |
| phantom-deps | phantom-dep:@rdfjs/data-model | AI (phantom-deps): Core RDF/JS data model used indirectly through generated vocabulary code; phantom-dep is a stable false positive for this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 5 / 4 |
v5.0.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.