@digital-realty/ix-switch
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 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.4.4 | 4 / 17 | |
| 2.4.2 | 4 / 17 | |
| 2.4.1 | 4 / 18 | |
| 2.3.12 | 4 / 21 | |
| 2.3.4 | 4 / 21 | |
| 2.3.3 | 4 / 21 | |
| 2.3.2 | 4 / 21 | |
| 2.3.1 | 4 / 21 | |
| 2.2.7 | 4 / 21 | |
| 2.2.6 | 4 / 21 | |
| 2.2.5 | 4 / 21 | |
| 2.2.4 | 4 / 20 | |
| 2.2.3 | 4 / 20 | |
| 2.1.12 | 4 / 20 | |
| 2.1.11 | 4 / 20 | |
| 2.1.10 | 4 / 20 |
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.
v2.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.