← Home

@instructure/ui-prop-types

npm Repository Homepage
22
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

jakeoedinginstuicimaths22jcrystalitadminsinstructure-toolsmiths-service-useraogata-instpkovaacskyler-instructureericsaupexcudderjdewarjozsefg-instructurejacksonhowekaroly.bujtor.instructureevatapaisarahgerardkercsojforbidwolfbencefarkasodmehbvikingpingvinajmal-esarobinkuss64david.wenzlick.instrazorsh4rkardenabpjatacsukangela.gombanatearmstronginstjoyenjoyercguanzon-instherrtopimatyas.szabocjs118camraydmz985ppesti-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 publisher-changed AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation; consistent with org-wide CI migration for this established package. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainer ppesti-inst is part of Instructure org; consistent with legitimate team change. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of mstarkman consistent with org-level maintainer rotation, not takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI-published release with SLSA provenance; not indicative of takeover for this established package. ai

Versions (showing 22 of 22)

Version Deps Published
10.30.0 2 / 4
10.29.0 2 / 4
10.26.4 2 / 4
10.26.3 2 / 4
10.26.2 2 / 4
10.26.1 2 / 4
10.26.0 2 / 4
10.25.0 2 / 4
10.24.2 2 / 4
10.24.1 2 / 4
10.24.0 2 / 4
10.23.0 2 / 4
10.22.0 2 / 4
10.21.0 2 / 4
10.20.1 2 / 4
10.20.0 2 / 4
10.19.1 2 / 4
10.19.0 2 / 4
10.18.1 2 / 4
10.18.0 2 / 4
10.17.0 2 / 4
10.16.4 2 / 4

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

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.

v10.26.2

1 finding
LOW No provenance attestation provenance

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

v10.26.1

1 finding
LOW No provenance attestation provenance

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

v10.26.0

1 finding
LOW No provenance attestation provenance

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

v10.25.0

1 finding
LOW No provenance attestation provenance

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

v10.24.2

1 finding
LOW No provenance attestation provenance

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

v10.24.1

1 finding
LOW No provenance attestation provenance

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

v10.24.0

1 finding
LOW No provenance attestation provenance

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

v10.23.0

1 finding
LOW No provenance attestation provenance

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

v10.22.0

1 finding
LOW No provenance attestation provenance

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

v10.21.0

1 finding
LOW No provenance attestation provenance

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

v10.20.1

1 finding
LOW No provenance attestation provenance

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

v10.20.0

1 finding
LOW No provenance attestation provenance

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

v10.19.1

1 finding
LOW No provenance attestation provenance

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

v10.19.0

1 finding
LOW No provenance attestation provenance

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

v10.18.1

1 finding
LOW No provenance attestation provenance

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

v10.18.0

1 finding
LOW No provenance attestation provenance

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

v10.17.0

1 finding
LOW No provenance attestation provenance

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

v10.16.4

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.