@digital-realty/ix-button
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 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.5.6 | 7 / 17 | |
| 3.5.4 | 7 / 17 | |
| 3.5.3 | 7 / 18 | |
| 3.5.1 | 7 / 18 | |
| 3.4.16 | 7 / 20 | |
| 3.4.5 | 6 / 20 | |
| 3.4.4 | 6 / 20 | |
| 3.4.3 | 6 / 20 | |
| 3.4.2 | 6 / 20 | |
| 3.4.1 | 5 / 20 | |
| 3.3.8 | 5 / 20 | |
| 3.3.7 | 5 / 20 | |
| 3.3.6 | 5 / 20 | |
| 3.3.5 | 5 / 19 | |
| 3.3.4 | 5 / 19 | |
| 3.3.3 | 4 / 19 | |
| 3.2.32 | 4 / 19 | |
| 3.2.31 | 4 / 19 |
v3.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
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 (nicholasnewlands) than the most recent previously approved version (dlr-pi-devops) on 2024-10-08, but nicholasnewlands 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.2.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.