@digital-realty/ix-email-list
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@web/test-runner-commands | AI (dependencies): @web/test-runner-commands is a well-known open-wc test utility; misplaced in dependencies but poses no runtime security risk. | ai | |
| phantom-deps | phantom-dep:@web/test-runner-commands | AI (phantom-deps): Test-runner utility miscategorized as runtime dep; not actually imported at runtime. Stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 6 / 17 | |
| 1.3.15 | 6 / 19 | |
| 1.3.7 | 6 / 19 | |
| 1.3.6 | 6 / 19 | |
| 1.3.5 | 6 / 19 | |
| 1.3.4 | 6 / 19 | |
| 1.3.3 | 6 / 19 | |
| 1.3.2 | 6 / 19 | |
| 1.3.1 | 6 / 19 | |
| 1.2.15 | 6 / 19 |
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.