@colijnit/articleapi
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
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 300.1.1 | 2 / 12 | |
| 300.1.0 | 2 / 12 | |
| 262.1.4 | 2 / 12 | |
| 262.1.3 | 2 / 12 | |
| 262.1.0 | 2 / 12 | |
| 261.1.5 | 2 / 12 | |
| 261.1.4 | 2 / 12 | |
| 261.1.0 | 2 / 12 |
v300.1.1
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 (patrickvkeulen) than the most recent previously approved version (ralf.eversen) on 2026-07-24, but patrickvkeulen 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.
v300.1.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 (ralf.eversen) than the most recent previously approved version (patrickvkeulen) on 2026-07-13, but ralf.eversen 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.
v261.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.