neo-blessed
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
iurimatias
Keywords
cursestuitputterminfotermcap
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Terminal UI library legitimately uses child_process for terminal/tty detection; stable pattern across versions. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in tput capability string parsing — standard pattern for terminfo handling in blessed/neo-blessed. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires in an example file (blessed-telnet.js) for module reloading; not in runtime library code. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating Sigstore provenance; absence is expected for packages of this age. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.2.0 | 0 / 0 |
v0.2.0
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.