@bunli/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): @bunli/tui is a TUI plugin for the Bunli CLI framework; name similarity to uuid is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @bunli/tui is a TUI plugin for the Bunli CLI framework; name similarity to joi is coincidental. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @bunli/tui is a TUI plugin for the Bunli CLI framework; name similarity to yup is coincidental. | ai | |
| phantom-deps | phantom-dep:debug | AI (phantom-deps): debug is a declared runtime dep; phantom-dep heuristic fires on config-file references, stable false positive. | ai | |
| phantom-deps | phantom-dep:@standard-schema/utils | AI (phantom-deps): @standard-schema/utils is a declared runtime dep; phantom-dep heuristic fires on config-file references, stable false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 7 / 5 | |
| 0.3.4 | 3 / 4 | |
| 0.3.2 | 3 / 4 | |
| 0.3.1 | 3 / 4 | |
| 0.3.0 | 3 / 4 | |
| 0.2.0 | 3 / 4 |
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.