← Home

@nextui-org/form

npm Repository Homepage
9
Versions
—
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

form

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped @nextui-org package; edit-distance match to 'cors' is coincidental, not a typosquat. ai
phantom-deps phantom-dep:@nextui-org/react-utils AI (phantom-deps): Same-org sibling dep; likely re-exported or used indirectly via build output. ai
phantom-deps phantom-dep:@nextui-org/shared-utils AI (phantom-deps): Same-org sibling dep; likely re-exported or used indirectly via build output. ai

Versions (showing 9 of 9)

Version Deps Published
2.1.8 8 / 0
2.1.7 8 / 0
2.1.6 8 / 0
2.1.5 8 / 0
2.1.4 8 / 0
2.1.3 8 / 0
2.1.2 8 / 0
2.1.1 8 / 0
2.1.0 8 / 0

v2.1.7

1 finding
LOW No provenance attestation provenance

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

v2.1.6

1 finding
LOW No provenance attestation provenance

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

v2.1.5

1 finding
LOW No provenance attestation provenance

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

v2.1.4

1 finding
LOW No provenance attestation provenance

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

v2.1.3

1 finding
LOW No provenance attestation provenance

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

v2.1.2

1 finding
LOW No provenance attestation provenance

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

v2.1.1

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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