← Home

@heroui/badge

npm Repository Homepage

Badges are used as a small numerical value or status descriptor for UI elements.

13
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

juniorgarciadev

Keywords

badge

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): HeroUI monorepo does not publish with Sigstore provenance; consistent across all versions. ai

Versions (showing 13 of 13)

Version Deps Published
2.2.18 2 / 0
2.2.17 2 / 0
2.2.16 2 / 0
2.2.15 2 / 0
2.2.14 2 / 0
2.2.13 2 / 0
2.2.12 2 / 0
2.2.11 2 / 0
2.2.10 2 / 0
2.2.9 2 / 0
2.2.7 2 / 0
2.2.6 2 / 0
2.2.5 2 / 0

v2.2.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.