@heroui/alert
Alerts are temporary notifications that provide concise feedback about an action or event.
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 package; provenance not yet adopted across the ecosystem for this org. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 2.2.32 | 5 / 0 | |
| 2.2.31 | 5 / 0 | |
| 2.2.30 | 5 / 0 | |
| 2.2.29 | 5 / 0 | |
| 2.2.28 | 5 / 0 | |
| 2.2.27 | 5 / 0 | |
| 2.2.26 | 5 / 0 | |
| 2.2.25 | 5 / 0 | |
| 2.2.24 | 5 / 0 | |
| 2.2.23 | 5 / 0 | |
| 2.2.22 | 6 / 0 | |
| 2.2.21 | 6 / 0 | |
| 2.2.20 | 6 / 0 | |
| 2.2.19 | 6 / 0 | |
| 2.2.18 | 6 / 0 | |
| 2.2.17 | 6 / 0 | |
| 2.2.16 | 6 / 0 | |
| 2.2.15 | 6 / 0 | |
| 2.2.14 | 6 / 0 | |
| 2.2.13 | 6 / 0 | |
| 2.2.11 | 6 / 0 | |
| 2.2.10 | 6 / 0 | |
| 2.2.9 | 6 / 0 |
v2.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.13
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.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.