← Home

@instructure/ui-navigation

npm Repository Homepage

Main and application level navigational 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
publish-pattern new-deps-added AI (publish-pattern): New dep is same-org same-version sibling; consistent with monorepo internal refactoring. ai
maintainer-change maintainer-added AI (maintainer-change): ppesti-inst is an Instructure org member; maintainer rotation within the same org is expected. ai
maintainer-change maintainer-removed AI (maintainer-change): mstarkman removal paired with org-internal addition is consistent with normal team rotation, not a takeover. ai
provenance publisher-changed AI (provenance): Instructure monorepo migrated publishing to GitHub Actions CI with SLSA attestation; expected pattern for this org. ai
dependencies unvetted-dep:@instructure/ui-testable AI (dependencies): Same @instructure org scope; standard testing utility within the monorepo. ai
dependencies unvetted-dep:@instructure/ui-prop-types AI (dependencies): Same @instructure org scope; standard prop-types utility within the monorepo. ai
phantom-deps phantom-dep:@instructure/ui-focusable AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. ai
phantom-deps phantom-dep:@instructure/debounce AI (phantom-deps): Same-org monorepo dep; may be used transitively or conditionally. ai
phantom-deps phantom-dep:@instructure/ui-a11y-utils AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. ai
phantom-deps phantom-dep:@instructure/ui-badge AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. ai
phantom-deps phantom-dep:@instructure/ui-icons AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. ai
phantom-deps phantom-dep:@instructure/ui-utils AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. ai
phantom-deps phantom-dep:@instructure/ui-tooltip AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. ai
phantom-deps phantom-dep:@instructure/ui-dom-utils AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. ai

Versions (showing 15 of 15)

Version Deps Published
11.7.3 18 / 8
11.7.2 17 / 9
11.7.1 17 / 9
11.7.0 17 / 9
11.6.0 17 / 9
11.5.0 17 / 9
11.4.0 17 / 9
11.3.0 17 / 9
11.2.0 17 / 9
11.0.1 17 / 9
11.0.0 17 / 9
10.30.0 20 / 9
10.29.0 20 / 9
10.26.4 20 / 9
10.26.3 20 / 9

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. Consider requesting the maintainer enable provenance via CI/CD.

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

2 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-02-20) provenance

This version was published by a different npm account than previous versions on 2026-02-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.

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.