@sk-web-gui/icon
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 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.1.2 | 1 / 1 | |
| 3.1.1 | 1 / 1 | |
| 3.1.0 | 1 / 1 | |
| 3.0.2 | 1 / 1 | |
| 3.0.1 | 1 / 1 | |
| 3.0.0 | 2 / 1 |
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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 (devizetim) than the most recent previously approved version (jerkerosatiesk) on 2025-01-30, but devizetim 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.
v3.0.2
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 (devizetim) than the most recent previously approved version (jerkerosatiesk) on 2025-01-02, but devizetim 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.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.