@heroui/tabs
Tabs organize content into multiple sections and allow users to navigate between them.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@heroui/framer-utils | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic fires on transitive/re-exported usage, stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@heroui/use-update-effect | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic fires on transitive/re-exported usage, stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@react-types/tabs | AI (phantom-deps): Type-only dependency used in config/type declarations; not directly imported at runtime, stable FP. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.2.29 | 10 / 0 | |
| 2.2.28 | 10 / 0 | |
| 2.2.27 | 10 / 0 | |
| 2.2.26 | 10 / 0 | |
| 2.2.25 | 10 / 0 | |
| 2.2.24 | 10 / 0 | |
| 2.2.23 | 10 / 0 | |
| 2.2.22 | 10 / 0 | |
| 2.2.21 | 10 / 0 | |
| 2.2.20 | 10 / 0 | |
| 2.2.19 | 11 / 0 | |
| 2.2.18 | 11 / 0 | |
| 2.2.17 | 14 / 0 | |
| 2.2.16 | 14 / 0 | |
| 2.2.15 | 14 / 0 | |
| 2.2.14 | 14 / 0 | |
| 2.2.13 | 14 / 0 | |
| 2.2.12 | 14 / 0 | |
| 2.2.11 | 14 / 0 | |
| 2.2.8 | 14 / 0 | |
| 2.2.7 | 14 / 0 |
v2.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.