@instructure/ui-menu
A dropdown menu component
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @instructure/ui-themes at the same pinned monorepo version; clearly an internal sibling package addition. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is a minor CI config change, not a supply chain risk for this established package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are all Instructure org members; consistent with org-level team management in a large monorepo. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of mstarkman alongside addition of multiple Instructure org members indicates a routine team transition, not a takeover. | ai | |
| dependencies | unvetted-dep:@instructure/ui-prop-types | AI (dependencies): Same-org Instructure package pinned to matching version 10.30.0; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@instructure/ui-testable | AI (dependencies): Same-org Instructure package pinned to matching version 10.30.0; not a third-party risk. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions CI with SLSA provenance; this is the expected pattern for automated releases in the Instructure monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; no provenance is consistent across all versions of this package family. | ai | |
| dependencies | unvetted-dep:@instructure/emotion | AI (dependencies): Same-org monorepo sibling, pinned to matching version. | ai | |
| phantom-deps | phantom-dep:@instructure/ui-view | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo re-exports. | ai | |
| dependencies | unvetted-dep:@instructure/ui-view | AI (dependencies): Same-org monorepo sibling, pinned to matching version. | ai | |
| dependencies | unvetted-dep:@instructure/ui-icons | AI (dependencies): Same-org monorepo sibling, pinned to matching version. | ai | |
| dependencies | unvetted-dep:@instructure/ui-utils | AI (dependencies): Same-org monorepo sibling, pinned to matching version. | ai | |
| dependencies | unvetted-dep:@instructure/ui-popover | AI (dependencies): Same-org monorepo sibling, pinned to matching version. | ai | |
| dependencies | unvetted-dep:@instructure/ui-position | AI (dependencies): Same-org monorepo sibling, pinned to matching version. | ai | |
| dependencies | unvetted-dep:@instructure/ui-a11y-utils | AI (dependencies): Same-org monorepo sibling, pinned to matching version. | ai | |
| dependencies | unvetted-dep:@instructure/ui-react-utils | AI (dependencies): Same-org monorepo sibling, pinned to matching version. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.7.3 | 14 / 7 | |
| 11.7.2 | 13 / 8 | |
| 11.7.1 | 13 / 8 | |
| 11.7.0 | 13 / 8 | |
| 11.6.0 | 13 / 8 | |
| 11.5.0 | 13 / 8 | |
| 11.4.0 | 13 / 8 | |
| 11.3.0 | 13 / 8 | |
| 11.2.0 | 13 / 8 | |
| 11.0.1 | 13 / 8 | |
| 11.0.0 | 13 / 8 | |
| 10.30.0 | 16 / 8 | |
| 10.29.0 | 16 / 8 | |
| 10.26.4 | 16 / 8 | |
| 10.26.3 | 16 / 8 |
v11.7.3
2 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.7.1
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.