@scaleflex/ui
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 7 of 7)
| 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 |
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.