@instructure/ui-a11y-utils
A collection of utilities for managing focus and screen reader behavior
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): GitHub Actions publish environment change explains missing gitHead; SLSA attestation compensates. | ai | |
| provenance | publisher-changed | AI (provenance): Instructure migrated publishing to GitHub Actions CI/CD; SLSA attestation confirms integrity. Stable pattern for this org's monorepo. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer ppesti-inst is consistent with org-level team rotation at Instructure; no malicious indicators. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of mstarkman consistent with org team rotation; no takeover indicators given SLSA attestation and clean diff. | ai | |
| dependencies | unvetted-dep:@instructure/uid | AI (dependencies): Sibling monorepo package co-released at same version; not an independent risk. | ai | |
| dependencies | unvetted-dep:@instructure/ui-dom-utils | AI (dependencies): Sibling monorepo package co-released at same version; not an independent risk. | ai | |
| dependencies | unvetted-dep:@instructure/ui-react-utils | AI (dependencies): Sibling monorepo package co-released at same version; not an independent risk. | ai | |
| dependencies | unvetted-dep:@instructure/ui-a11y-content | AI (dependencies): Sibling monorepo package co-released at same version; not an independent risk. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.7.3 | 8 / 5 | |
| 11.7.2 | 8 / 5 | |
| 11.7.1 | 8 / 5 | |
| 11.7.0 | 8 / 5 | |
| 11.6.0 | 8 / 5 | |
| 11.5.0 | 8 / 5 | |
| 11.4.0 | 8 / 5 | |
| 11.3.0 | 8 / 5 | |
| 11.2.0 | 8 / 5 | |
| 11.0.1 | 8 / 5 | |
| 11.0.0 | 8 / 5 | |
| 10.30.0 | 8 / 5 | |
| 10.29.0 | 8 / 5 | |
| 10.26.4 | 8 / 5 | |
| 10.26.3 | 8 / 5 |
v11.7.3
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v11.7.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-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.
v11.7.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-18. 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.
v11.6.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-02-18. 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.
v11.5.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-02-03. 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.
v11.4.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-01-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.
v11.3.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-01-12. 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.
v11.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.30.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-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.
v10.29.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-15. 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.
v10.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.