@digital-realty/ix-select
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 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 1.3.4 | 7 / 16 | |
| 1.3.2 | 7 / 16 | |
| 1.3.1 | 7 / 17 | |
| 1.2.16 | 7 / 20 | |
| 1.2.8 | 7 / 20 | |
| 1.2.6 | 7 / 20 | |
| 1.2.5 | 5 / 20 | |
| 1.2.4 | 5 / 20 | |
| 1.2.3 | 5 / 20 | |
| 1.2.2 | 5 / 20 | |
| 1.2.1 | 5 / 20 | |
| 1.1.14 | 5 / 20 | |
| 1.1.13 | 5 / 20 | |
| 1.1.12 | 5 / 20 | |
| 1.1.11 | 5 / 20 | |
| 1.1.10 | 5 / 20 | |
| 1.1.9 | 5 / 20 | |
| 1.1.8 | 5 / 19 | |
| 1.1.7 | 5 / 19 | |
| 1.1.6 | 5 / 19 | |
| 1.1.5 | 5 / 19 | |
| 1.1.4 | 5 / 19 | |
| 1.1.3 | 5 / 19 | |
| 1.0.39 | 5 / 19 | |
| 1.0.38 | 5 / 19 | |
| 1.0.37 | 5 / 19 | |
| 1.0.36 | 5 / 19 |
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
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.
v1.1.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.
v1.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.