@instructure/ui-responsive
A component that allows for rendering a component differently based on either the element or the viewport size
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 cosmetic given verified CI/CD publish chain. | ai | |
| provenance | publisher-changed | AI (provenance): Instructure migrated publishing to GitHub Actions CI with SLSA attestation; this is the expected new publisher for this org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are within the Instructure org; consistent with team rotation at a large org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal paired with org-internal additions; consistent with legitimate team transition. | ai | |
| phantom-deps | phantom-dep:@instructure/ui-testable | AI (phantom-deps): Same org scope (@instructure); phantom-dep false positive common in monorepo builds where deps are used transitively. | ai | |
| phantom-deps | phantom-dep:@instructure/ui-react-utils | AI (phantom-deps): Same-org scope dep used transitively; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Babel runtime is a transitive convention dep, not directly imported; stable false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.7.3 | 7 / 5 | |
| 11.7.2 | 7 / 5 | |
| 11.7.1 | 7 / 5 | |
| 11.7.0 | 7 / 5 | |
| 11.6.0 | 7 / 5 | |
| 11.5.0 | 7 / 5 | |
| 11.4.0 | 7 / 5 | |
| 11.3.0 | 7 / 5 | |
| 11.2.0 | 7 / 5 | |
| 11.0.1 | 7 / 5 | |
| 11.0.0 | 7 / 5 | |
| 10.30.0 | 9 / 5 | |
| 10.29.0 | 9 / 5 | |
| 10.26.4 | 9 / 5 | |
| 10.26.3 | 9 / 5 |
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. 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
1 findingPublished 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.