@heroui/user
Flexible User Profile Component.
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): Established heroui monorepo; provenance not yet adopted across the org, consistent across all versions. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 2.2.26 | 4 / 0 | |
| 2.2.25 | 4 / 0 | |
| 2.2.24 | 4 / 0 | |
| 2.2.23 | 4 / 0 | |
| 2.2.22 | 4 / 0 | |
| 2.2.21 | 4 / 0 | |
| 2.2.20 | 4 / 0 | |
| 2.2.19 | 4 / 0 | |
| 2.2.18 | 5 / 0 | |
| 2.2.17 | 5 / 0 | |
| 2.2.16 | 5 / 0 | |
| 2.2.15 | 5 / 0 | |
| 2.2.14 | 5 / 0 | |
| 2.2.13 | 5 / 0 | |
| 2.2.12 | 5 / 0 | |
| 2.2.11 | 5 / 0 | |
| 2.2.10 | 5 / 0 | |
| 2.2.8 | 5 / 0 | |
| 2.2.7 | 5 / 0 | |
| 2.2.6 | 5 / 0 |
v2.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.