← Home

axe-core

npm Repository Homepage

Accessibility engine for automated Web UI testing

6
Versions
MPL-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

dylanbwilcofiersdqlabsnpmdeque

Keywords

Accessibilitya11ytestingunittddbddaxe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI/CD publishing with SLSA provenance; expected for dequelabs/axe-core. ai
publish-pattern dormant-publish AI (publish-pattern): Package has 1523 versions; gap is between approved versions, not true dormancy. ai
license weak-copyleft-license:MPL-2.0 AI (license): MPL-2.0 is axe-core's longstanding license; stable across versions. ai

Versions (showing 6 of 6)

Version Deps Published
4.11.4 0 / 69
4.11.3 0 / 69
4.11.2 0 / 69
4.11.1 0 / 69
4.11.0 0 / 70
4.10.3 0 / 70

v4.11.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.11.2

2 findings
HIGH Publisher changed: npmdeque → GitHub Actions (on 2026-03-31) provenance

This version was published by a different npm account than previous versions on 2026-03-31. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.11.1

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: npmdeque → GitHub Actions (on 2026-01-06) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-01-06. This could indicate a legitimate maintainer transition or an account compromise.

v4.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.10.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.