← Home

@heroui/divider

. A separator is a visual divider between two groups of content

19
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

divider

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
phantom-deps phantom-dep:@heroui/shared-utils AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on indirect usage patterns common in monorepos. ai

Versions (showing 19 of 19)

Version Deps Published
2.2.24 3 / 0
2.2.23 3 / 0
2.2.22 3 / 0
2.2.21 3 / 0
2.2.20 3 / 0
2.2.19 3 / 0
2.2.18 3 / 0
2.2.17 3 / 0
2.2.16 3 / 0
2.2.15 3 / 0
2.2.14 4 / 0
2.2.13 4 / 0
2.2.12 4 / 0
2.2.11 4 / 0
2.2.10 4 / 0
2.2.9 4 / 0
2.2.7 4 / 0
2.2.6 4 / 0
2.2.5 4 / 0

v2.2.11

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.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.