← Home

@instructure/ui-source-code-editor

npm Repository Homepage

A UI component library made by Instructure Inc.

15
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

jakeoedinginstuicimaths22jcrystalitadminsaogata-instpkovaacskyler-instructureericsaupexcudderjdewarjozsefg-instructurejacksonhowekaroly.bujtor.instructureevatapaisarahgerardkercsojforbidwolfbencefarkasodmehbvikingpingvinajmal-esarobinkuss64david.wenzlick.instrazorsh4rkardenabpjatacsukangela.gombanatearmstronginstjoyenjoyercguanzon-instherrtopimatyas.szabocjs118camraydmz985kristofkulcsarinstructure-npm-write-svc-accountmhulse_instsvetlintanyimhogensonppesti-instaaronshafszilard.doro-instmartongreczi-instinstoutsvcquizzesnpmbalazs.buri.instructuredaniel-torokfmarcsopeipeizhouis-adamszaborajmund-instdanny-instructure

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): SLSA provenance attestation present; missing gitHead is a minor metadata gap, not a supply chain risk for this package. ai
maintainer-change maintainer-added AI (maintainer-change): Large org package; maintainer roster changes are routine and publishing is now gated through CI/CD with provenance. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of mstarkman alongside org-wide CI migration is consistent with legitimate maintainer transition. ai
provenance publisher-changed AI (provenance): Instructure migrated publishing to GitHub Actions CI with SLSA attestation; stable pattern for this org's monorepo. ai
semgrep semgrep:dynamic-require AI (semgrep): React version compat shim with explicit comment; not arbitrary module loading. ai
dependencies unvetted-dep:@instructure/ui-testable AI (dependencies): First-party Instructure monorepo package pinned to same version; stable pattern. ai
dependencies unvetted-dep:@instructure/ui-prop-types AI (dependencies): First-party Instructure monorepo package pinned to same version; stable pattern. ai
dependencies unvetted-dep:@instructure/ui-react-utils AI (dependencies): Sibling monorepo package; co-versioned releases are expected. ai
dependencies unvetted-dep:@instructure/emotion AI (dependencies): Sibling monorepo package; co-versioned releases are expected. ai
dependencies unvetted-dep:@instructure/ui-a11y-content AI (dependencies): Sibling monorepo package; co-versioned releases are expected. ai
dependencies unvetted-dep:@instructure/ui-i18n AI (dependencies): Sibling monorepo package; co-versioned releases are expected. ai
dependencies unvetted-dep:@instructure/ui-icons AI (dependencies): Sibling monorepo package; co-versioned releases are expected. ai
dependencies unvetted-dep:@instructure/ui-utils AI (dependencies): Sibling monorepo package; co-versioned releases are expected. ai
dependencies unvetted-dep:@instructure/ui-themes AI (dependencies): Sibling monorepo package; co-versioned releases are expected. ai
dependencies unvetted-dep:@instructure/ui-buttons AI (dependencies): Sibling monorepo package; co-versioned releases are expected. ai
dependencies unvetted-dep:@instructure/ui-text-input AI (dependencies): Sibling monorepo package; co-versioned releases are expected. ai

Versions (showing 15 of 15)

Version Deps Published
11.7.3 26 / 5
11.7.2 26 / 5
11.7.1 26 / 5
11.7.0 26 / 5
11.6.0 26 / 5
11.5.0 26 / 5
11.4.0 26 / 5
11.3.0 26 / 5
11.2.0 26 / 5
11.0.1 26 / 5
11.0.0 26 / 5
10.30.0 29 / 5
10.29.0 29 / 5
10.26.4 29 / 5
10.26.3 29 / 5

v11.7.3

2 findings
HIGH Missing gitHead — previous versions had it provenance

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.

INFO Has SLSA provenance attestation provenance

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 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-03-20) provenance

This 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.

INFO Has SLSA provenance attestation provenance

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 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-03-18) provenance

This 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.

INFO Has SLSA provenance attestation provenance

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 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-02-18) provenance

This 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.

INFO Has SLSA provenance attestation provenance

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 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-02-03) provenance

This 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.

INFO Has SLSA provenance attestation provenance

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 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-01-20) provenance

This 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.

INFO Has SLSA provenance attestation provenance

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 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-01-12) provenance

This 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.

INFO Has SLSA provenance attestation provenance

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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.30.0

1 finding
INFO Has SLSA provenance attestation provenance

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 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-01-15) provenance

This 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.

INFO Has SLSA provenance attestation provenance

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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.26.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.