@digital-realty/ix-file-uploader
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@material/web | AI (phantom-deps): Material Design dependency for web component styling; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:@lit-labs/react | AI (phantom-deps): React adapter for Lit components; used via exports, not direct import in main code. | ai | |
| phantom-deps | phantom-dep:@digital-realty/ix-button | AI (phantom-deps): Sibling component in same org; used via re-export, not direct import. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.3.2 | 8 / 17 | |
| 1.3.1 | 8 / 17 | |
| 1.2.21 | 8 / 19 | |
| 1.2.13 | 8 / 19 | |
| 1.2.12 | 8 / 19 | |
| 1.2.11 | 8 / 19 | |
| 1.2.10 | 8 / 19 | |
| 1.2.9 | 8 / 19 | |
| 1.2.8 | 8 / 19 | |
| 1.2.7 | 8 / 19 | |
| 1.2.6 | 8 / 19 | |
| 1.2.5 | 8 / 19 | |
| 1.2.4 | 8 / 19 | |
| 1.2.3 | 8 / 19 | |
| 1.2.2 | 8 / 19 | |
| 1.2.1 | 8 / 19 | |
| 1.1.15 | 8 / 19 | |
| 1.1.14 | 7 / 19 |
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.