@instructure/ui-code-editor
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 | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; consistent with org-wide CI/CD migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects monorepo release cadence, not suspicious activity; SLSA attestation confirms CI provenance. | ai | |
| phantom-deps | phantom-dep:@instructure/ui-utils | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for intra-monorepo deps. | ai | |
| phantom-deps | phantom-dep:@instructure/ui-dom-utils | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for intra-monorepo deps. | ai | |
| phantom-deps | phantom-dep:@instructure/ui-color-utils | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for intra-monorepo deps. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 10.30.0 | 11 / 3 | |
| 10.29.0 | 11 / 3 | |
| 10.26.4 | 11 / 3 | |
| 10.26.3 | 11 / 3 | |
| 10.26.2 | 11 / 3 | |
| 10.26.1 | 11 / 3 | |
| 10.26.0 | 11 / 3 | |
| 10.25.0 | 11 / 3 | |
| 10.24.2 | 11 / 3 | |
| 10.24.1 | 11 / 3 | |
| 10.24.0 | 11 / 3 | |
| 10.23.0 | 11 / 3 | |
| 10.22.0 | 11 / 3 | |
| 10.21.0 | 11 / 3 | |
| 10.20.1 | 12 / 4 | |
| 10.20.0 | 12 / 4 | |
| 10.19.1 | 12 / 4 | |
| 10.19.0 | 12 / 4 | |
| 10.18.1 | 12 / 4 | |
| 10.18.0 | 12 / 4 | |
| 10.17.0 | 12 / 4 | |
| 10.16.4 | 12 / 4 |
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.
v10.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.