@instructure/ui-view
A component for basic styles including spacing, sizing, borders, display, positioning, and focus states.
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; gitHead absence is superseded by Sigstore attestation for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Instructure migrated publishing to GitHub Actions CI/CD with SLSA attestation; stable pattern for this org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Internal Instructure team rotation; consistent with org-level CI/CD migration. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of mstarkman consistent with internal team rotation, not a hostile takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Both added deps (prop-types, @instructure/ui-prop-types) are standard React ecosystem packages expected in an Instructure UI component. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.7.3 | 10 / 5 | |
| 11.7.2 | 9 / 6 | |
| 11.7.1 | 9 / 6 | |
| 11.7.0 | 9 / 6 | |
| 11.6.0 | 9 / 6 | |
| 11.5.0 | 9 / 6 | |
| 11.4.0 | 9 / 6 | |
| 11.3.0 | 9 / 6 | |
| 11.2.0 | 9 / 6 | |
| 11.0.1 | 9 / 6 | |
| 11.0.0 | 10 / 6 | |
| 10.30.0 | 11 / 6 | |
| 10.29.0 | 11 / 6 | |
| 10.26.4 | 11 / 6 | |
| 10.26.3 | 11 / 6 |
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. Consider requesting the maintainer enable provenance via CI/CD.