← Home

@draht/tui

npm Repository

Terminal User Interface library with differential rendering for efficient text-based applications

9
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

execute008

Keywords

tuiterminaluitext-editordifferential-renderingtypescriptcli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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, not impersonation. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped TUI library; name similarity to yup is coincidental, not impersonation. ai
phantom-deps phantom-dep:chalk AI (phantom-deps): chalk is a declared runtime dep in a TUI library; likely re-exported or used indirectly. ai
phantom-deps phantom-dep:mime-types AI (phantom-deps): mime-types is a declared runtime dep; framework-style usage is plausible. ai
phantom-deps phantom-dep:@types/mime-types AI (phantom-deps): Type-only package loaded by convention; false positive for this package. ai

Versions (showing 9 of 9)

Version Deps Published
2026.4.26 5 / 2
2026.4.25 5 / 2
2026.4.23 5 / 2
2026.4.5 5 / 2
2026.3.14 5 / 2
2026.3.5 5 / 2
2026.3.4 5 / 2
2026.3.3 6 / 2
2026.3.2 6 / 2

v2026.4.26

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.4.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2026.4.23

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2026.4.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.3.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2026.3.5

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: execute008.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2026.3.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.