← Home

@instructure/ui

npm Repository Homepage

A meta package exporting all UI components

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): CI/CD migration to GitHub Actions explains missing gitHead; SLSA attestation provides stronger provenance. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainer ppesti-inst is an Instructure org account; consistent with org-level CI transition. ai
provenance publisher-changed AI (provenance): Instructure org migrated publishing to GitHub Actions CI; consistent with SLSA attestation present. ai
dependencies unvetted-dep:@instructure/ui-modal AI (dependencies): Sibling package in the same monorepo release; not an external risk. ai
dependencies unvetted-dep:@instructure/ui-tray AI (dependencies): Sibling package in the same monorepo release; not an external risk. ai
dependencies unvetted-dep:@instructure/ui-buttons AI (dependencies): Sibling package in the same monorepo release; not an external risk. ai
dependencies unvetted-dep:@instructure/ui-drilldown AI (dependencies): Sibling package in the same monorepo release; not an external risk. ai
dependencies unvetted-dep:@instructure/ui-code-editor AI (dependencies): Sibling package in the same monorepo release; not an external risk. ai
dependencies unvetted-dep:@instructure/ui-date-time-input AI (dependencies): Sibling package in the same monorepo release; not an external risk. ai
typosquat typosquat.levenshtein:joi AI (typosquat): False positive; @instructure/ui is a legitimate scoped UI library, not a typosquat of 'joi'. ai
typosquat typosquat.levenshtein:yup AI (typosquat): False positive; @instructure/ui is a legitimate scoped UI library, not a typosquat of 'yup'. ai
phantom-deps phantom-dep:@babel/runtime AI (phantom-deps): @babel/runtime is a runtime helper injected by Babel transforms; not directly imported but legitimately required. ai
typosquat typosquat.levenshtein:qs AI (typosquat): False positive; @instructure/ui is a legitimate scoped UI library, not a typosquat of 'qs'. ai
typosquat typosquat.levenshtein:uuid AI (typosquat): Scoped @instructure/ui package; Levenshtein match to 'uuid' is a false positive for this well-known design system. ai
typosquat typosquat.levenshtein:pg AI (typosquat): False positive; @instructure/ui is a legitimate scoped UI library, not a typosquat of 'pg'. ai

Versions (showing 15 of 15)

Version Deps Published
11.7.3 74 / 1
11.7.2 74 / 1
11.7.1 74 / 1
11.7.0 74 / 1
11.6.0 74 / 1
11.5.0 74 / 1
11.4.0 74 / 1
11.3.0 74 / 1
11.2.0 74 / 1
11.0.1 74 / 1
11.0.0 74 / 1
10.30.0 75 / 1
10.29.0 75 / 1
10.26.4 75 / 1
10.26.3 75 / 1

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

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

v11.5.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.

v11.4.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.

v11.3.0

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.