@heroui/input
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:@react-types/shared | AI (phantom-deps): @react-types/shared is a declared runtime dep used for TypeScript types; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): HeroUI monorepo does not publish with Sigstore provenance; consistent across all versions. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 2.4.33 | 12 / 0 | |
| 2.4.32 | 12 / 0 | |
| 2.4.31 | 12 / 0 | |
| 2.4.30 | 12 / 0 | |
| 2.4.29 | 12 / 0 | |
| 2.4.28 | 12 / 0 | |
| 2.4.27 | 12 / 0 | |
| 2.4.26 | 12 / 0 | |
| 2.4.25 | 12 / 0 | |
| 2.4.24 | 12 / 0 | |
| 2.4.23 | 12 / 0 | |
| 2.4.22 | 13 / 0 | |
| 2.4.21 | 13 / 0 | |
| 2.4.20 | 13 / 0 | |
| 2.4.19 | 13 / 0 | |
| 2.4.17 | 13 / 0 | |
| 2.4.16 | 13 / 0 | |
| 2.4.15 | 13 / 0 | |
| 2.4.13 | 13 / 0 | |
| 2.4.10 | 13 / 0 | |
| 2.4.9 | 13 / 0 | |
| 2.4.8 | 13 / 0 |
v2.4.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.