@arbidocs/tui
Interactive terminal UI for ARBI — chat-style RAG assistant with streaming responses
Supply chain provenance
Status for the latest visible version.
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
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 @arbidocs/tui; no plausible impersonation of uuid. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @arbidocs/tui; no plausible impersonation of joi. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @arbidocs/tui; no plausible impersonation of yup. | ai | |
| dependencies | unvetted-dep:fake-indexeddb | AI (dependencies): fake-indexeddb is a well-known IndexedDB polyfill for Node; legitimate use in a RAG/chat TUI. | ai |
Versions (showing 26 of 126)
| Version | Deps | Published |
|---|---|---|
| 0.3.35 | 7 / 3 | |
| 0.3.34 | 7 / 3 | |
| 0.3.33 | 7 / 3 | |
| 0.3.32 | 7 / 3 | |
| 0.3.31 | 7 / 3 | |
| 0.3.30 | 7 / 3 | |
| 0.3.29 | 7 / 3 | |
| 0.3.28 | 7 / 3 | |
| 0.3.27 | 7 / 3 | |
| 0.3.26 | 7 / 3 | |
| 0.3.25 | 7 / 3 | |
| 0.3.24 | 7 / 3 | |
| 0.3.23 | 7 / 3 | |
| 0.3.22 | 7 / 3 | |
| 0.3.21 | 7 / 3 | |
| 0.3.20 | 7 / 3 | |
| 0.3.19 | 7 / 3 | |
| 0.3.18 | 7 / 3 | |
| 0.3.17 | 7 / 3 | |
| 0.3.16 | 7 / 3 | |
| 0.3.15 | 7 / 3 | |
| 0.3.14 | 7 / 3 | |
| 0.3.13 | 7 / 3 | |
| 0.3.11 | 7 / 3 | |
| 0.3.10 | 7 / 3 | |
| 0.1.0 | 7 / 3 |
v0.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.