@leaflink/dom-testing-utils
Frontend DOM testing utilities
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher is a documented automation pattern; consistent with org-level CI/CD adoption. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.3.2 | 1 / 12 | |
| 5.3.1 | 1 / 12 | |
| 5.3.0 | 1 / 8 | |
| 5.2.2 | 1 / 7 | |
| 5.2.1 | 1 / 7 | |
| 5.2.0 | 1 / 7 | |
| 5.1.0 | 1 / 7 | |
| 5.0.0 | 1 / 7 |
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.