@easbot/tui
EASBot Terminal User Interface library - A fully autonomous TUI rendering engine ported and extended from pi-tui
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 TUI library; name similarity to uuid is coincidental substring overlap, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped TUI library; name similarity to joi is coincidental substring overlap, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped TUI library; name similarity to yup is coincidental substring overlap, not impersonation. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is a declared runtime dep; phantom-dep heuristic likely misses indirect usage in bundled output. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): mime-types is a declared runtime dep; phantom-dep heuristic likely misses indirect usage in bundled output. | ai | |
| phantom-deps | phantom-dep:@types/mime-types | AI (phantom-deps): Type-only dep; framework-scoped, loaded by convention as noted by analyzer. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.2.0 | 6 / 2 | |
| 0.1.15 | 6 / 2 | |
| 0.1.14 | 6 / 2 | |
| 0.1.13 | 6 / 2 | |
| 0.1.11 | 6 / 2 | |
| 0.1.7 | 6 / 2 |
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jallenhou.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.