@enso-ui/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 @enso-ui package; no relation to uuid. Stable false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @enso-ui package; no relation to pg. Stable false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @enso-ui package; no relation to qs. Stable false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @enso-ui package; no relation to joi. Stable false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @enso-ui package; no relation to yup. Stable false positive. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 7.1.55 | 1 / 51 | |
| 7.1.54 | 1 / 51 | |
| 7.1.52 | 1 / 50 | |
| 7.1.51 | 1 / 50 | |
| 7.1.50 | 2 / 50 | |
| 7.1.49 | 1 / 50 | |
| 7.1.48 | 1 / 50 | |
| 7.1.46 | 1 / 50 | |
| 7.1.45 | 1 / 50 | |
| 7.1.44 | 1 / 50 | |
| 7.1.43 | 1 / 50 | |
| 7.1.42 | 1 / 50 | |
| 7.1.41 | 1 / 50 | |
| 7.1.40 | 1 / 50 | |
| 7.1.39 | 1 / 50 | |
| 7.1.38 | 1 / 50 | |
| 7.1.37 | 1 / 50 | |
| 7.1.36 | 1 / 50 | |
| 7.1.35 | 1 / 50 | |
| 7.1.34 | 1 / 50 | |
| 7.1.32 | 1 / 50 | |
| 7.1.31 | 1 / 50 | |
| 7.1.30 | 1 / 43 | |
| 7.1.29 | 1 / 43 | |
| 7.1.28 | 1 / 43 | |
| 7.1.27 | 1 / 43 | |
| 7.1.26 | 1 / 43 | |
| 7.1.25 | 1 / 43 | |
| 7.1.24 | 1 / 43 | |
| 7.1.23 | 1 / 43 | |
| 7.1.22 | 1 / 43 | |
| 7.1.21 | 1 / 43 | |
| 7.1.19 | 1 / 43 | |
| 7.1.18 | 1 / 43 | |
| 7.1.17 | 1 / 43 | |
| 7.1.15 | 1 / 43 | |
| 7.1.13 | 1 / 43 | |
| 7.1.12 | 1 / 43 | |
| 7.1.11 | 1 / 43 | |
| 7.1.10 | 1 / 43 | |
| 7.1.9 | 1 / 43 | |
| 7.1.8 | 1 / 43 | |
| 7.0.1 | 41 / 0 | |
| 7.0.0 | 41 / 0 | |
| 6.2.7 | 62 / 9 | |
| 6.2.6 | 62 / 9 |
v7.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.