@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 — 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 @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 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 0.3.85 | 7 / 4 | |
| 0.3.84 | 7 / 4 | |
| 0.3.83 | 7 / 4 | |
| 0.3.82 | 7 / 4 | |
| 0.3.81 | 7 / 4 | |
| 0.3.80 | 7 / 4 | |
| 0.3.79 | 7 / 4 | |
| 0.3.78 | 7 / 4 | |
| 0.3.77 | 7 / 4 | |
| 0.3.76 | 7 / 4 | |
| 0.3.75 | 7 / 4 | |
| 0.3.74 | 7 / 4 | |
| 0.3.73 | 7 / 4 | |
| 0.3.72 | 7 / 4 | |
| 0.3.71 | 7 / 4 | |
| 0.3.70 | 7 / 4 | |
| 0.3.69 | 7 / 4 | |
| 0.3.68 | 7 / 4 | |
| 0.3.67 | 7 / 4 | |
| 0.3.66 | 7 / 3 | |
| 0.3.65 | 7 / 3 | |
| 0.3.64 | 7 / 3 | |
| 0.3.63 | 7 / 3 | |
| 0.3.62 | 7 / 3 | |
| 0.3.61 | 7 / 3 | |
| 0.3.60 | 7 / 3 | |
| 0.3.59 | 7 / 3 | |
| 0.3.58 | 7 / 3 | |
| 0.3.57 | 7 / 3 | |
| 0.3.56 | 7 / 3 | |
| 0.3.55 | 7 / 3 | |
| 0.3.54 | 7 / 3 | |
| 0.3.53 | 7 / 3 | |
| 0.3.52 | 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 |
v0.3.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.