@citation-js/plugin-wikidata
5
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
larsgw
Keywords
citation-jswikidatawikicite
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo packages commonly release together in quick succession; benign here. | ai | |
| dependencies | unvetted-dep:@citation-js/date | AI (dependencies): Sibling package in same citation-js monorepo, maintained by same publisher. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived monorepo package with irregular release cadence, not indicative of takeover. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.8.1 | 3 / 1 | |
| 0.8.0 | 3 / 1 | |
| 0.7.22 | 3 / 1 | |
| 0.7.21 | 3 / 1 | |
| 0.7.20 | 3 / 1 |
v0.8.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.20
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.