← Home

@nomos-ui/common

npm Repository Homepage
18
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

uanela

Keywords

reactreact-hook-formformformsvalidationcomponentsuiinputselectcheckboxaccessiblea11ytailwindtypescriptnomos

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@tailwindcss/vite AI (phantom-deps): Build tooling declared for Vite config; not directly imported in source is expected. ai
phantom-deps phantom-dep:@tailwindcss/postcss AI (phantom-deps): PostCSS config tooling; phantom-dep false positive for this package. ai
phantom-deps phantom-dep:@radix-ui/react-slot AI (phantom-deps): Radix slot used transitively via config/re-exports; stable false positive. ai
phantom-deps phantom-dep:class-variance-authority AI (phantom-deps): CVA used in component config patterns; phantom-dep false positive for this UI library. ai
phantom-deps phantom-dep:@radix-ui/react-hover-card AI (phantom-deps): Radix hover-card referenced in config/re-exports; stable false positive for this package. ai
phantom-deps phantom-dep:@nomos-ui/core AI (phantom-deps): Same-org monorepo sibling; declared as runtime dep, phantom-dep heuristic is a false positive here. ai

Versions (showing 18 of 18)

Version Deps Published
0.5.1 5 / 13
0.5.0 5 / 13
0.4.0 4 / 13
0.3.2 5 / 13
0.3.1 0 / 13
0.3.0 1 / 13
0.2.9 0 / 13
0.2.8 0 / 13
0.2.7 0 / 13
0.2.6 1 / 13
0.2.5 1 / 13
0.2.4 1 / 13
0.2.3 1 / 13
0.1.3 0 / 13
0.1.2 0 / 13
0.1.1 10 / 13
0.1.0 10 / 13
0.0.2 10 / 13

v0.5.1

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

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

v0.3.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.2.9

1 finding
LOW No provenance attestation provenance

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

v0.2.8

1 finding
LOW No provenance attestation provenance

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

v0.2.7

1 finding
LOW No provenance attestation provenance

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

v0.2.6

1 finding
LOW No provenance attestation provenance

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

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.4

1 finding
LOW No provenance attestation provenance

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

v0.2.3

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

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

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

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

v0.0.2

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.