@instructure/ui-select
A component for select and autocomplete 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): SLSA provenance attestation present; missing gitHead is a minor metadata gap, not a supply chain risk for this well-established package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org packages at matching pinned versions plus well-known prop-types; no supply chain risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Instructure org maintainer rotation; consistent with large org package management. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Instructure org maintainer rotation; consistent with large org package management. | ai | |
| provenance | publisher-changed | AI (provenance): Instructure monorepo migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@instructure/ui-testable | AI (dependencies): Same-org monorepo dep pinned to matching version; consistent with Instructure UI release pattern. | ai | |
| dependencies | unvetted-dep:@instructure/ui-prop-types | AI (dependencies): Same-org monorepo dep pinned to matching version; consistent with Instructure UI release pattern. | ai | |
| phantom-deps | phantom-dep:@instructure/uid | AI (phantom-deps): @instructure/uid is explicitly declared as a runtime dependency in package.json; phantom-dep is a false positive for this monorepo package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.7.3 | 16 / 7 | |
| 11.7.2 | 15 / 8 | |
| 11.7.1 | 15 / 8 | |
| 11.7.0 | 15 / 8 | |
| 11.6.0 | 15 / 8 | |
| 11.5.0 | 15 / 8 | |
| 11.4.0 | 15 / 8 | |
| 11.3.0 | 15 / 8 | |
| 11.2.0 | 15 / 8 | |
| 11.0.1 | 15 / 8 | |
| 11.0.0 | 15 / 8 | |
| 10.30.0 | 18 / 8 | |
| 10.29.0 | 18 / 8 | |
| 10.26.4 | 18 / 8 | |
| 10.26.3 | 18 / 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.