@colijnit/configuratorcore
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 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 300.1.0 | 4 / 0 | |
| 262.1.6 | 4 / 0 | |
| 262.1.5 | 4 / 0 | |
| 262.1.4 | 4 / 0 | |
| 262.1.3 | 4 / 0 | |
| 262.1.2 | 6 / 0 | |
| 262.1.1 | 8 / 0 | |
| 262.1.0 | 8 / 0 | |
| 261.1.3 | 4 / 0 | |
| 261.1.2 | 6 / 0 | |
| 261.1.1 | 8 / 0 |
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 (jilliscit) 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.
v262.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v262.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v261.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.