← Home

@neynar/ui

npm
12
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

manan-neynarshreyaschorgelucas-neynarrishmbob-neynar

Keywords

reactuicomponentstailwindbase-uineynar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:uuid AI (typosquat): Scoped UI library; Levenshtein match to uuid is coincidental, not a squatting attempt. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped UI library; Levenshtein match to pg is coincidental. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped UI library; Levenshtein match to qs is coincidental. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped UI library; Levenshtein match to joi is coincidental. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped UI library; Levenshtein match to yup is coincidental. ai
phantom-deps phantom-dep:@fontsource-variable/figtree AI (phantom-deps): Font package referenced in CSS/config, not JS imports; phantom-dep heuristic doesn't apply. ai
phantom-deps phantom-dep:@fontsource/architects-daughter AI (phantom-deps): Font package referenced in CSS/config, not JS imports; phantom-dep heuristic doesn't apply. ai

Versions (showing 12 of 12)

Version Deps Published
1.2.2 11 / 35
1.2.1 11 / 35
1.2.0 11 / 35
1.1.0 11 / 35
1.0.6 11 / 35
1.0.5 11 / 35
1.0.4 11 / 35
1.0.3 11 / 35
1.0.2 11 / 35
1.0.1 11 / 35
1.0.0 11 / 35
0.5.0 11 / 35

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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

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