clownface
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
ludovicm67zazuko-bot
Keywords
rdfgraphtraversing
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@rdfjs/namespace | AI (dependencies): @rdfjs/namespace is a canonical RDF.js ecosystem package; expected and appropriate dependency for an RDF graph library. | ai | |
| dependencies | unvetted-dep:@rdfjs/data-model | AI (dependencies): @rdfjs/data-model is a canonical RDF.js ecosystem package; expected and appropriate dependency for an RDF graph library. | ai | |
| dependencies | unvetted-dep:@rdfjs/environment | AI (dependencies): @rdfjs/environment is a canonical RDF.js ecosystem package; expected and appropriate dependency for an RDF graph library. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating widespread Sigstore adoption; lack of provenance is not a security concern here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.0.3 | 3 / 16 |
v2.0.3
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.