@digital-realty/ix-drawer
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 66 of 66)
| Version | Deps | Published |
|---|---|---|
| 1.3.6 | 8 / 16 | |
| 1.3.4 | 8 / 16 | |
| 1.3.3 | 8 / 17 | |
| 1.3.2 | 8 / 17 | |
| 1.3.1 | 8 / 17 | |
| 1.2.20 | 8 / 20 | |
| 1.2.12 | 8 / 20 | |
| 1.2.11 | 8 / 20 | |
| 1.2.10 | 8 / 20 | |
| 1.2.9 | 8 / 20 | |
| 1.2.8 | 8 / 20 | |
| 1.2.7 | 8 / 20 | |
| 1.2.6 | 8 / 20 | |
| 1.2.5 | 8 / 20 | |
| 1.2.4 | 8 / 20 | |
| 1.2.3 | 8 / 20 | |
| 1.2.2 | 8 / 20 | |
| 1.2.1 | 8 / 20 | |
| 1.1.31 | 8 / 20 | |
| 1.1.30 | 8 / 20 | |
| 1.1.29 | 8 / 20 | |
| 1.1.28 | 8 / 20 | |
| 1.1.27 | 8 / 20 | |
| 1.1.26 | 8 / 20 | |
| 1.1.25 | 8 / 20 | |
| 1.1.24 | 8 / 20 | |
| 1.1.23 | 8 / 20 | |
| 1.1.22 | 8 / 20 | |
| 1.1.21 | 8 / 20 | |
| 1.1.20 | 8 / 20 | |
| 1.1.19 | 8 / 20 | |
| 1.1.18 | 8 / 19 | |
| 1.1.17 | 8 / 19 | |
| 1.1.16 | 8 / 19 | |
| 1.1.15 | 8 / 19 | |
| 1.1.14 | 8 / 19 | |
| 1.1.13 | 8 / 19 | |
| 1.1.12 | 8 / 19 | |
| 1.1.11 | 8 / 19 | |
| 1.1.10 | 8 / 19 | |
| 1.1.9 | 8 / 19 | |
| 1.1.8 | 8 / 19 | |
| 1.1.7 | 8 / 19 | |
| 1.1.6 | 8 / 19 | |
| 1.1.5 | 8 / 19 | |
| 1.1.4 | 8 / 19 | |
| 1.1.3 | 8 / 19 | |
| 1.1.2 | 8 / 19 | |
| 1.0.45 | 8 / 19 | |
| 1.0.44 | 8 / 19 | |
| 1.0.43 | 8 / 19 | |
| 1.0.42 | 8 / 19 | |
| 1.0.41 | 8 / 19 | |
| 1.0.40 | 8 / 19 | |
| 1.0.39 | 8 / 19 | |
| 1.0.38 | 8 / 19 | |
| 1.0.37 | 8 / 19 | |
| 1.0.36 | 8 / 19 | |
| 1.0.35 | 8 / 19 | |
| 1.0.34 | 8 / 19 | |
| 1.0.33 | 8 / 19 | |
| 1.0.32 | 8 / 19 | |
| 1.0.31 | 8 / 19 | |
| 1.0.30 | 8 / 19 | |
| 1.0.29 | 8 / 19 | |
| 1.0.28 | 8 / 19 |
v1.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1.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 (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.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.