vitest-axe
Custom Vitest matcher for testing accessibility with aXe. Forked from jest-axe.
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): vitest-axe legitimately uses 0.0.0 as its initial version; package has 601k weekly downloads, 1389 days of age, and a trusted publisher. Not a malicious throwaway. | ai | |
| phantom-deps | phantom-dep:redent | AI (phantom-deps): redent is a declared runtime dependency used by this accessibility utility; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:aria-query | AI (phantom-deps): aria-query is a declared runtime dependency for accessibility querying; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:dom-accessibility-api | AI (phantom-deps): dom-accessibility-api is a declared runtime dependency for accessibility testing; phantom detection is a false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.1.0 | 6 / 16 | |
| 0.0.7 | 6 / 16 | |
| 0.0.6 | 6 / 16 | |
| 0.0.5 | 6 / 16 | |
| 0.0.4 | 6 / 16 | |
| 0.0.0 | 6 / 16 |
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.