@enablerr-ui/app
enablerr - the Next Enterprise Solution
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:hapi | AI (typosquat): Scoped package @enablerr-ui/app is not a plausible typosquat of hapi; brand is clearly distinct. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @enablerr-ui/app is not a plausible typosquat of pg; brand is clearly distinct. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @enablerr-ui/app is not a plausible typosquat of yup; brand is clearly distinct. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @enablerr-ui/app is not a plausible typosquat of ajv; brand is clearly distinct. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.2.26 | 0 / 0 | |
| 0.2.25 | 0 / 0 | |
| 0.2.24 | 0 / 0 | |
| 0.2.23 | 0 / 0 |
v0.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.