@instructure/ui-top-nav-bar
A UI component library made by Instructure Inc.
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 | missing-githead | AI (provenance): Instructure migrated to GitHub Actions CI with SLSA attestation; gitHead absence is expected in this publish flow. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Maintainer roster changes consistent with org-level CI/CD migration; not indicative of takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual maintainer consistent with transition to automated publishing; no malicious signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All three new deps are well-known packages (prop-types) or same-org Instructure UI packages; not suspicious. | ai | |
| provenance | publisher-changed | AI (provenance): Instructure migrated publishing to GitHub Actions CI/CD with SLSA attestation; stable pattern for this org's packages. | ai | |
| dependencies | unvetted-dep:@instructure/ui-utils | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-avatar | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-dialog | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-buttons | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-popover | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-tooltip | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/emotion | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-breadcrumb | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-responsive | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-react-utils | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-a11y-content | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-truncate-list | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-drilldown | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-link | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-tray | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-view | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai | |
| dependencies | unvetted-dep:@instructure/ui-icons | AI (dependencies): Sibling monorepo package; same version pinning is expected for @instructure/* releases. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.7.3 | 22 / 8 | |
| 11.7.2 | 21 / 9 | |
| 11.7.1 | 21 / 9 | |
| 11.7.0 | 21 / 9 | |
| 11.6.0 | 21 / 9 | |
| 11.5.0 | 21 / 9 | |
| 11.4.0 | 21 / 9 | |
| 11.3.0 | 21 / 9 | |
| 11.2.0 | 21 / 9 | |
| 11.0.1 | 21 / 9 | |
| 11.0.0 | 21 / 9 | |
| 10.30.0 | 24 / 9 | |
| 10.29.0 | 24 / 9 | |
| 10.26.4 | 24 / 9 | |
| 10.26.3 | 24 / 9 |
v11.7.3
2 findingsThis 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.7.1
3 findingsThis 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.
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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.7.0
3 findingsThis 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.
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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.6.0
3 findingsThis 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.
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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.5.0
3 findingsThis 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.
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.
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 findingsThis 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.
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 findingsThis 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.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.30.0
2 findingsThis 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.
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 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. Consider requesting the maintainer enable provenance via CI/CD.
v10.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.