← Home

@florexlabs/ui

Dark-first React component library by Florex Labs — 46+ accessible components, design tokens, and Tailwind CSS v4 integration for building modern web applications.

4
Versions
MIT
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

devflorezflorex

Keywords

florexflorexlabsuireactcomponentscomponent-librarydesign-systemtailwindcsstailwinddark-themedark-modetypescriptaccessiblea11yphosphor-iconscvaclass-variance-authority

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:uuid AI (typosquat): Scoped brand package @florexlabs/ui; not a plausible typosquat of uuid. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped brand package @florexlabs/ui; not a plausible typosquat of pg. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped brand package @florexlabs/ui; not a plausible typosquat of qs. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped brand package @florexlabs/ui; not a plausible typosquat of joi. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped brand package @florexlabs/ui; not a plausible typosquat of yup. ai

Versions (showing 4 of 4)

Version Deps Published
0.1.3 3 / 19
0.1.2 3 / 19
0.1.1 3 / 17
0.1.0 3 / 17

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. Consider requesting the maintainer enable provenance via CI/CD.

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.