@instructure/ui-form-field
Form layout components.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of mstarkman alongside addition of multiple Instructure staff indicates routine team change, not takeover. | ai | |
| provenance | missing-githead | AI (provenance): Package has SLSA provenance attestation; missing gitHead reflects CI pipeline change, not supply chain risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Instructure employees (instructure-domain usernames); consistent with org team rotation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): prop-types is a well-known React ecosystem package; benign addition for this UI component library. | ai | |
| provenance | publisher-changed | AI (provenance): Instructure monorepo migrated publishing to GitHub Actions CI/CD with SLSA attestation; this is the expected pattern for this org. | ai | |
| phantom-deps | phantom-dep:@instructure/uid | AI (phantom-deps): Same-org monorepo sibling; may be used transitively, not a phantom dep concern. | ai | |
| phantom-deps | phantom-dep:@instructure/ui-utils | AI (phantom-deps): Same-org monorepo sibling; transitive usage is expected pattern. | ai | |
| phantom-deps | phantom-dep:@instructure/console | AI (phantom-deps): Same-org monorepo sibling; transitive usage is expected pattern. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.7.3 | 12 / 5 | |
| 11.7.2 | 11 / 6 | |
| 11.7.1 | 11 / 6 | |
| 11.7.0 | 11 / 6 | |
| 11.6.0 | 11 / 6 | |
| 11.5.0 | 11 / 6 | |
| 11.4.0 | 11 / 6 | |
| 11.3.0 | 11 / 6 | |
| 11.2.0 | 11 / 6 | |
| 11.0.1 | 11 / 6 | |
| 11.0.0 | 11 / 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 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This 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.
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
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.4.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.3.0
1 findingPublished 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. 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.