@mariozechner/pi-tui
Terminal User Interface library with differential rendering for efficient text-based applications
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is a declared dependency in a TUI library; phantom-dep flag is a code hygiene issue, not a security risk for this package. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): mime-types is a declared dependency; phantom-dep flag is a code hygiene issue, not a security risk for this package. | ai | |
| phantom-deps | phantom-dep:@types/mime-types | AI (phantom-deps): @types/mime-types is a type declaration package; phantom-dep flag is expected and not a security concern. | ai |
Versions (showing 100 of 309)
| Version | Deps | Published |
|---|---|---|
| 0.13.0 | 5 / 2 | |
| 0.12.15 | 5 / 2 | |
| 0.12.14 | 5 / 2 | |
| 0.12.13 | 5 / 2 | |
| 0.12.12 | 5 / 2 | |
| 0.12.11 | 5 / 2 | |
| 0.12.10 | 5 / 2 | |
| 0.12.9 | 5 / 2 | |
| 0.12.8 | 5 / 2 | |
| 0.12.7 | 5 / 2 | |
| 0.12.6 | 5 / 2 | |
| 0.12.5 | 5 / 2 | |
| 0.12.4 | 5 / 2 | |
| 0.12.3 | 5 / 2 | |
| 0.12.2 | 5 / 2 | |
| 0.12.1 | 5 / 2 | |
| 0.12.0 | 5 / 2 | |
| 0.11.6 | 5 / 2 | |
| 0.11.5 | 5 / 2 | |
| 0.11.4 | 5 / 2 | |
| 0.11.3 | 5 / 2 | |
| 0.11.2 | 5 / 2 | |
| 0.11.1 | 5 / 2 | |
| 0.11.0 | 5 / 2 | |
| 0.10.2 | 6 / 2 | |
| 0.10.1 | 6 / 2 | |
| 0.10.0 | 6 / 2 | |
| 0.9.4 | 5 / 2 | |
| 0.9.3 | 5 / 2 | |
| 0.9.2 | 5 / 2 | |
| 0.9.1 | 5 / 2 | |
| 0.9.0 | 5 / 2 | |
| 0.8.5 | 5 / 2 | |
| 0.8.4 | 5 / 2 | |
| 0.8.3 | 5 / 2 | |
| 0.8.2 | 5 / 2 | |
| 0.8.1 | 5 / 2 | |
| 0.7.29 | 5 / 2 | |
| 0.7.28 | 5 / 2 | |
| 0.7.27 | 5 / 2 | |
| 0.7.26 | 5 / 2 | |
| 0.7.25 | 5 / 2 | |
| 0.7.24 | 5 / 2 | |
| 0.7.23 | 5 / 2 | |
| 0.7.22 | 5 / 2 | |
| 0.7.21 | 5 / 2 | |
| 0.7.20 | 5 / 2 | |
| 0.7.18 | 5 / 2 | |
| 0.7.17 | 5 / 2 | |
| 0.7.16 | 5 / 2 | |
| 0.7.15 | 5 / 2 | |
| 0.7.13 | 5 / 2 | |
| 0.7.12 | 5 / 2 | |
| 0.7.11 | 5 / 2 | |
| 0.7.10 | 5 / 2 | |
| 0.7.9 | 5 / 2 | |
| 0.7.8 | 5 / 2 | |
| 0.7.7 | 5 / 2 | |
| 0.7.5 | 5 / 2 | |
| 0.7.2 | 5 / 2 | |
| 0.7.1 | 5 / 2 | |
| 0.7.0 | 5 / 2 | |
| 0.6.2 | 5 / 2 | |
| 0.5.48 | 4 / 2 | |
| 0.5.47 | 4 / 2 | |
| 0.5.46 | 4 / 2 | |
| 0.5.45 | 4 / 2 | |
| 0.5.44 | 4 / 2 | |
| 0.5.43 | 4 / 2 | |
| 0.5.42 | 4 / 2 | |
| 0.5.41 | 4 / 2 | |
| 0.5.40 | 4 / 2 | |
| 0.5.39 | 4 / 2 | |
| 0.5.38 | 4 / 2 | |
| 0.5.35 | 4 / 2 | |
| 0.5.34 | 4 / 2 | |
| 0.5.33 | 4 / 2 | |
| 0.5.32 | 4 / 2 | |
| 0.5.31 | 4 / 2 | |
| 0.5.30 | 4 / 2 | |
| 0.5.29 | 4 / 2 | |
| 0.5.28 | 4 / 2 | |
| 0.5.27 | 4 / 2 | |
| 0.5.26 | 4 / 2 | |
| 0.5.25 | 4 / 2 | |
| 0.5.24 | 4 / 2 | |
| 0.5.23 | 4 / 2 | |
| 0.5.22 | 4 / 2 | |
| 0.5.21 | 4 / 2 | |
| 0.5.20 | 4 / 2 | |
| 0.5.19 | 4 / 2 | |
| 0.5.18 | 4 / 2 | |
| 0.5.17 | 4 / 2 | |
| 0.5.16 | 4 / 2 | |
| 0.5.15 | 4 / 2 | |
| 0.5.14 | 4 / 2 | |
| 0.5.13 | 4 / 2 | |
| 0.5.12 | 4 / 2 | |
| 0.5.11 | 4 / 2 | |
| 0.5.10 | 4 / 2 |
v0.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.