@instructure/ui-instructure
Collection of specific components for Instructure products
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): CI/CD migration to GitHub Actions explains missing gitHead; SLSA attestation provides stronger provenance signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org @instructure packages at matching version 11.3.0; not third-party risk. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing is a legitimate pipeline change for this established Instructure monorepo. | ai | |
| dependencies | unvetted-dep:@instructure/ui-modal | AI (dependencies): Same-org monorepo sibling pinned to matching version; consistent release pattern across all @instructure/* deps. | ai | |
| phantom-deps | phantom-dep:@instructure/ui-testable | AI (phantom-deps): Same-org monorepo sibling; declared as runtime dep for testability hooks, not directly imported in main source. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types is a common React ecosystem peer; declared in package.json for compatibility, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@instructure/ui-view | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for transitive/re-export patterns. | ai | |
| phantom-deps | phantom-dep:@instructure/ui-react-utils | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for transitive/re-export patterns. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.7.3 | 13 / 6 | |
| 11.7.2 | 12 / 7 | |
| 11.7.1 | 12 / 7 | |
| 11.7.0 | 12 / 7 | |
| 11.6.0 | 12 / 7 | |
| 11.5.0 | 12 / 7 | |
| 11.4.0 | 12 / 7 | |
| 11.3.0 | 11 / 7 | |
| 11.2.0 | 11 / 7 | |
| 11.0.1 | 9 / 7 | |
| 11.0.0 | 9 / 7 | |
| 10.30.0 | 13 / 7 | |
| 10.29.0 | 13 / 7 | |
| 10.26.4 | 11 / 7 | |
| 10.26.3 | 11 / 7 |
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 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.0
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.6.0
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.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.4.0
1 findingPublished 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. 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
1 findingPublished 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.