← Home

@reifydb/ui

npm Repository Homepage

Shared UI component library for ReifyDB

10
Versions
Apache-2.0
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

ddymke

Keywords

reifydbuicomponentsreacttypescripttailwind

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:uuid AI (typosquat): Scoped package @reifydb/ui; 'ui' suffix coincidentally close to short package names, not a typosquat. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Same rationale — scoped org package, no impersonation intent. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Same rationale — scoped org package, no impersonation intent. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Same rationale — scoped org package, no impersonation intent. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Same rationale — scoped org package, no impersonation intent. ai

Versions (showing 10 of 10)

Version Deps Published
0.6.0 1 / 17
0.5.6 1 / 17
0.5.0 1 / 17
0.4.13 1 / 17
0.4.12 1 / 17
0.4.11 1 / 17
0.4.10 1 / 17
0.4.9 1 / 17
0.4.8 1 / 17
0.4.7 1 / 17

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.6

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

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

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

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

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

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

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

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.