focus-trap
Trap focus within a DOM node.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed from stefcameron to GitHub Actions as part of a legitimate migration to automated CI/CD publishing with SLSA provenance attestation. This is a supply chain improvement, not a compromise signal. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 8.2.1 | 1 / 47 | |
| 8.2.0 | 1 / 47 | |
| 8.1.0 | 1 / 47 | |
| 8.0.1 | 1 / 47 | |
| 8.0.0 | 1 / 47 | |
| 7.8.0 | 1 / 47 | |
| 7.7.1 | 1 / 47 | |
| 7.7.0 | 1 / 47 | |
| 7.6.6 | 1 / 38 | |
| 7.6.5 | 1 / 38 | |
| 7.6.4 | 1 / 38 | |
| 7.6.3 | 1 / 38 | |
| 7.6.2 | 1 / 28 | |
| 7.6.1 | 1 / 28 | |
| 7.6.0 | 1 / 29 | |
| 7.5.4 | 1 / 29 | |
| 7.5.3 | 1 / 29 | |
| 7.5.2 | 1 / 29 | |
| 7.5.1 | 1 / 29 | |
| 7.5.0 | 1 / 29 | |
| 7.4.3 | 1 / 29 | |
| 7.4.2 | 1 / 29 | |
| 7.4.1 | 1 / 29 | |
| 7.4.0 | 1 / 29 | |
| 7.3.1 | 1 / 29 | |
| 7.3.0 | 1 / 29 | |
| 7.2.0 | 1 / 29 | |
| 7.1.0 | 1 / 29 | |
| 7.0.0 | 1 / 29 | |
| 6.9.4 | 1 / 29 | |
| 6.9.3 | 1 / 29 | |
| 6.9.2 | 1 / 29 | |
| 6.9.1 | 1 / 29 | |
| 6.9.0 | 1 / 28 | |
| 6.8.1 | 1 / 28 | |
| 6.8.0 | 1 / 28 | |
| 6.7.3 | 1 / 28 | |
| 6.7.2 | 1 / 28 | |
| 6.7.1 | 1 / 28 | |
| 6.7.0 | 1 / 28 | |
| 6.6.1 | 1 / 28 | |
| 6.6.0 | 1 / 28 | |
| 6.5.1 | 1 / 28 | |
| 6.5.0 | 1 / 28 | |
| 6.4.0 | 1 / 27 | |
| 6.3.0 | 1 / 27 | |
| 6.2.3 | 1 / 26 | |
| 6.2.2 | 1 / 26 | |
| 6.2.1 | 1 / 26 | |
| 6.2.0 | 1 / 25 | |
| 6.1.4 | 1 / 25 |
v8.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.7.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.