@instructure/ui-position
A component for positioning content with respect to a designated target.
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/Sigstore attestation present; gitHead absence is minor for this well-established monorepo package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Added dep is same-org same-version sibling @instructure/ui-themes; consistent with monorepo release pattern. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Instructure org team expansion; all new maintainers are Instructure employees per handle patterns. | ai | |
| provenance | publisher-changed | AI (provenance): Instructure monorepo migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern going forward. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer rotation in a large org; no takeover indicators given SLSA provenance. | ai | |
| dependencies | unvetted-dep:@instructure/ui-testable | AI (dependencies): Same-org Instructure UI sibling package pinned to matching version; consistent with the monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@instructure/ui-prop-types | AI (dependencies): Same-org Instructure UI sibling package pinned to matching version; consistent with the monorepo release pattern. | ai | |
| phantom-deps | phantom-dep:@instructure/uid | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for this package. | 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 | 9 / 6 | |
| 10.30.0 | 12 / 6 | |
| 10.29.0 | 12 / 6 | |
| 10.26.4 | 12 / 6 | |
| 10.26.3 | 12 / 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. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.