@hyperspaceng/neural-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 directly imported for terminal styling; stable false positive. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): mime-types is directly imported for file type handling; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/mime-types | AI (phantom-deps): TypeScript types for mime-types; directly imported; stable false positive. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.70.7 | 5 / 2 | |
| 0.70.6 | 5 / 2 | |
| 0.70.3 | 5 / 2 | |
| 0.70.1 | 5 / 2 | |
| 0.69.1 | 5 / 2 | |
| 0.68.2 | 5 / 2 | |
| 0.68.1 | 5 / 2 | |
| 0.67.69 | 5 / 2 | |
| 0.67.7 | 5 / 2 | |
| 0.67.4 | 5 / 2 | |
| 0.67.3 | 5 / 2 | |
| 0.67.2 | 5 / 2 | |
| 0.66.2 | 5 / 2 | |
| 0.65.3 | 5 / 2 | |
| 0.65.1 | 5 / 2 | |
| 0.64.1 | 5 / 2 | |
| 0.63.2 | 5 / 2 | |
| 0.63.0 | 5 / 2 | |
| 0.62.1 | 5 / 2 | |
| 0.61.6 | 5 / 2 | |
| 0.61.5 | 5 / 2 | |
| 0.61.4 | 5 / 2 | |
| 0.61.3 | 5 / 2 | |
| 0.61.2 | 5 / 2 | |
| 0.60.0 | 5 / 2 |
v0.70.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.