← Home

@scaleflex/ui

npm Repository Homepage
10
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

dmitry.stremousvitaly.shaposhnikamr26ahmeeedmostafa

Keywords

reacttypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:uuid AI (typosquat): Scoped package @scaleflex/ui; Levenshtein match to uuid is a false positive for this established UI library. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package @scaleflex/ui; Levenshtein match to pg is a false positive for this established UI library. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @scaleflex/ui; Levenshtein match to qs is a false positive for this established UI library. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @scaleflex/ui; Levenshtein match to joi is a false positive for this established UI library. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped package @scaleflex/ui; Levenshtein match to yup is a false positive for this established UI library. ai
phantom-deps phantom-dep:@types/lodash.merge AI (phantom-deps): @types/lodash.merge is a TypeScript type declaration; not directly imported at runtime by convention. ai

Versions (showing 10 of 10)

Version Deps Published
3.0.9 6 / 2
3.0.8 6 / 2
3.0.7 6 / 2
3.0.6 6 / 2
3.0.5 6 / 2
3.0.4 6 / 2
3.0.3 6 / 2
3.0.2 6 / 2
3.0.1 6 / 2
3.0.0 6 / 2

v3.0.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vitaly.shaposhnik → amr26 (on 2025-05-13, known maintainer) provenance

This version was published by a different npm account (amr26) than the most recent previously approved version (vitaly.shaposhnik) on 2025-05-13, but amr26 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

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

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