@axe-core/playwright
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:axe-test-fixtures | AI (npm-metadata): Dev-only test fixture from official dequelabs org, not shipped in published package. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 4.12.1 | 1 / 12 | |
| 4.11.3 | 1 / 12 | |
| 4.11.2 | 1 / 12 | |
| 4.11.1 | 1 / 15 | |
| 4.11.0 | 1 / 15 | |
| 4.10.2 | 1 / 15 | |
| 4.10.1 | 1 / 15 | |
| 4.10.0 | 1 / 15 | |
| 4.9.1 | 1 / 15 | |
| 4.9.0 | 1 / 15 | |
| 4.8.5 | 1 / 15 | |
| 4.8.4 | 1 / 15 | |
| 4.8.3 | 1 / 15 | |
| 4.8.2 | 1 / 15 | |
| 4.8.1 | 1 / 16 | |
| 4.8.0 | 1 / 16 | |
| 4.7.3 | 1 / 16 | |
| 4.7.2 | 1 / 16 | |
| 4.7.1 | 1 / 17 | |
| 4.7.0 | 1 / 17 | |
| 4.6.1 | 1 / 16 | |
| 4.6.0 | 1 / 16 | |
| 4.5.2 | 1 / 16 | |
| 4.5.1 | 1 / 16 | |
| 4.5.0 | 1 / 16 | |
| 4.4.5 | 1 / 16 | |
| 4.4.4 | 2 / 14 | |
| 4.4.3 | 2 / 14 | |
| 4.4.2 | 2 / 14 | |
| 4.4.1 | 2 / 14 | |
| 4.4.0 | 2 / 14 | |
| 4.3.3 | 2 / 14 | |
| 4.3.2 | 2 / 14 | |
| 4.3.1 | 2 / 14 | |
| 4.3.0 | 2 / 14 | |
| 4.2.2 | 2 / 13 |
v4.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.