@digital-realty/ix-grid
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:rollup-plugin-replace | AI (phantom-deps): rollup-plugin-replace is a build-time dep mistakenly listed in dependencies; not a real phantom-dep security concern. | ai |
Versions (showing 100 of 107)
| Version | Deps | Published |
|---|---|---|
| 1.4.5 | 15 / 21 | |
| 1.4.3 | 15 / 21 | |
| 1.4.2 | 15 / 22 | |
| 1.4.1 | 15 / 22 | |
| 1.3.11 | 15 / 24 | |
| 1.3.10 | 15 / 24 | |
| 1.3.9 | 14 / 24 | |
| 1.3.8 | 14 / 24 | |
| 1.3.7 | 14 / 24 | |
| 1.3.6 | 14 / 24 | |
| 1.3.5 | 14 / 24 | |
| 1.3.4 | 14 / 24 | |
| 1.3.3 | 14 / 24 | |
| 1.3.2 | 14 / 24 | |
| 1.3.1 | 14 / 24 | |
| 1.2.44 | 14 / 24 | |
| 1.2.43 | 14 / 24 | |
| 1.2.42 | 14 / 24 | |
| 1.2.41 | 14 / 24 | |
| 1.2.40 | 14 / 24 | |
| 1.2.39 | 14 / 24 | |
| 1.2.38 | 14 / 24 | |
| 1.2.37 | 14 / 24 | |
| 1.2.36 | 14 / 24 | |
| 1.2.35 | 14 / 24 | |
| 1.2.34 | 14 / 24 | |
| 1.2.33 | 14 / 24 | |
| 1.2.32 | 14 / 24 | |
| 1.2.31 | 14 / 24 | |
| 1.2.30 | 14 / 24 | |
| 1.2.29 | 14 / 24 | |
| 1.2.28 | 14 / 24 | |
| 1.2.26 | 14 / 23 | |
| 1.2.25 | 14 / 23 | |
| 1.2.24 | 14 / 23 | |
| 1.2.23 | 14 / 23 | |
| 1.2.22 | 14 / 23 | |
| 1.2.21 | 14 / 23 | |
| 1.2.9 | 15 / 23 | |
| 1.2.8 | 15 / 23 | |
| 1.2.7 | 14 / 23 | |
| 1.2.6 | 14 / 23 | |
| 1.2.5 | 14 / 23 | |
| 1.2.4 | 14 / 23 | |
| 1.2.3 | 14 / 23 | |
| 1.2.2 | 14 / 23 | |
| 1.2.1 | 14 / 23 | |
| 1.1.30 | 14 / 23 | |
| 1.1.29 | 14 / 23 | |
| 1.1.28 | 14 / 23 | |
| 1.1.27 | 14 / 23 | |
| 1.1.26 | 14 / 23 | |
| 1.1.25 | 14 / 23 | |
| 1.1.24 | 14 / 23 | |
| 1.1.23 | 13 / 23 | |
| 1.1.22 | 13 / 23 | |
| 1.1.21 | 13 / 23 | |
| 1.1.20 | 13 / 22 | |
| 1.1.19 | 13 / 22 | |
| 1.1.18 | 13 / 22 | |
| 1.1.17 | 13 / 22 | |
| 1.1.16 | 13 / 22 | |
| 1.1.15 | 13 / 22 | |
| 1.1.14 | 13 / 20 | |
| 1.1.13 | 13 / 20 | |
| 1.1.12 | 13 / 20 | |
| 1.1.11 | 13 / 20 | |
| 1.1.10 | 13 / 20 | |
| 1.1.9 | 12 / 20 | |
| 1.1.8 | 12 / 20 | |
| 1.1.7 | 12 / 20 | |
| 1.1.6 | 12 / 20 | |
| 1.1.5 | 12 / 20 | |
| 1.1.4 | 12 / 20 | |
| 1.0.60 | 10 / 20 | |
| 1.0.59 | 10 / 19 | |
| 1.0.58 | 10 / 19 | |
| 1.0.57 | 10 / 19 | |
| 1.0.54 | 10 / 19 | |
| 1.0.53 | 10 / 19 | |
| 1.0.52 | 10 / 19 | |
| 1.0.51 | 10 / 19 | |
| 1.0.50 | 10 / 19 | |
| 1.0.49 | 10 / 19 | |
| 1.0.48 | 10 / 19 | |
| 1.0.47 | 10 / 19 | |
| 1.0.46 | 10 / 19 | |
| 1.0.45 | 10 / 19 | |
| 1.0.44 | 10 / 19 | |
| 1.0.43 | 10 / 19 | |
| 1.0.42 | 10 / 19 | |
| 1.0.41 | 10 / 19 | |
| 1.0.40 | 10 / 19 | |
| 1.0.39 | 10 / 19 | |
| 1.0.38 | 10 / 19 | |
| 1.0.37 | 10 / 19 | |
| 1.0.36 | 10 / 19 | |
| 1.0.35 | 10 / 19 | |
| 1.0.34 | 10 / 19 | |
| 1.0.33 | 10 / 19 |
v1.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.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 2025-03-27, 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.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 2025-03-14, 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.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
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.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.