@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, 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 |
|---|---|---|---|---|
| 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 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 1.4.4 | 6 / 16 | |
| 1.4.2 | 6 / 16 | |
| 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 | |
| 1.2.14 | 6 / 19 | |
| 1.2.13 | 6 / 19 | |
| 1.2.12 | 6 / 19 | |
| 1.2.11 | 7 / 19 | |
| 1.2.10 | 7 / 18 | |
| 1.2.9 | 7 / 18 | |
| 1.2.8 | 7 / 18 | |
| 1.2.7 | 7 / 18 | |
| 1.2.6 | 7 / 18 | |
| 1.2.5 | 7 / 18 | |
| 1.2.4 | 7 / 18 | |
| 1.2.3 | 7 / 18 | |
| 1.1.41 | 7 / 18 | |
| 1.1.40 | 7 / 18 | |
| 1.1.39 | 7 / 18 | |
| 1.1.38 | 7 / 18 | |
| 1.1.37 | 7 / 18 | |
| 1.1.36 | 7 / 18 | |
| 1.1.35 | 7 / 18 | |
| 1.1.34 | 7 / 18 | |
| 1.1.33 | 7 / 18 | |
| 1.1.32 | 7 / 18 | |
| 1.1.31 | 7 / 18 | |
| 1.1.30 | 7 / 18 | |
| 1.1.29 | 7 / 18 | |
| 1.1.28 | 7 / 18 |
v1.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 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.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.31
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. Only ~12% of npm packages have provenance, so this is common but not ideal.