@heroui/system
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): HeroUI org consistently publishes without Sigstore provenance; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@react-stately/utils | AI (phantom-deps): @react-stately/utils is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 2.4.28 | 5 / 0 | |
| 2.4.27 | 5 / 0 | |
| 2.4.26 | 5 / 0 | |
| 2.4.25 | 5 / 0 | |
| 2.4.24 | 5 / 0 | |
| 2.4.23 | 5 / 0 | |
| 2.4.22 | 5 / 0 | |
| 2.4.21 | 5 / 0 | |
| 2.4.20 | 5 / 0 | |
| 2.4.19 | 5 / 0 | |
| 2.4.18 | 5 / 0 | |
| 2.4.17 | 6 / 0 | |
| 2.4.16 | 8 / 0 | |
| 2.4.15 | 8 / 0 | |
| 2.4.14 | 8 / 0 | |
| 2.4.13 | 8 / 0 | |
| 2.4.12 | 8 / 0 | |
| 2.4.11 | 8 / 0 | |
| 2.4.10 | 8 / 0 | |
| 2.4.8 | 8 / 0 | |
| 2.4.7 | 8 / 0 | |
| 2.4.6 | 8 / 0 |
v2.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.10
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.