@heroui/navbar
A responsive navigation header positioned on top side of your page that includes support for branding, links, navigation, collapse and more.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Provenance absent across all versions; not a regression for this package. | ai | |
| dependencies | unvetted-dep:@heroui/react-utils | AI (dependencies): First-party heroui monorepo sibling package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@heroui/framer-utils | AI (dependencies): First-party heroui monorepo sibling package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@heroui/use-resize | AI (dependencies): First-party heroui monorepo sibling package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@heroui/dom-animation | AI (dependencies): First-party heroui monorepo sibling package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@heroui/use-scroll-position | AI (dependencies): First-party heroui monorepo sibling package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@heroui/shared-utils | AI (dependencies): First-party heroui monorepo sibling package; stable false positive for this org. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.2.30 | 12 / 0 | |
| 2.2.28 | 12 / 0 | |
| 2.2.27 | 12 / 0 | |
| 2.2.26 | 12 / 0 | |
| 2.2.25 | 12 / 0 | |
| 2.2.24 | 12 / 0 | |
| 2.2.23 | 12 / 0 | |
| 2.2.22 | 12 / 0 | |
| 2.2.21 | 12 / 0 | |
| 2.2.20 | 12 / 0 | |
| 2.2.19 | 12 / 0 | |
| 2.2.18 | 12 / 0 | |
| 2.2.17 | 12 / 0 | |
| 2.2.16 | 12 / 0 | |
| 2.2.9 | 12 / 0 |
v2.2.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.