@earendil-works/pi-tui
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Change is to GitHub Actions CI/CD with SLSA attestation — provenance improvement, not compromise. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Win32 console-mode .node files are expected native bindings for a TUI library; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/mime-types | AI (phantom-deps): Framework-scoped convention; stable pattern for this package. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.82.1 | 2 / 2 | |
| 0.82.0 | 2 / 2 | |
| 0.81.1 | 2 / 2 | |
| 0.81.0 | 2 / 2 | |
| 0.80.10 | 2 / 2 | |
| 0.80.9 | 2 / 2 | |
| 0.80.8 | 2 / 2 | |
| 0.80.7 | 2 / 2 | |
| 0.80.6 | 2 / 2 | |
| 0.80.5 | 2 / 2 | |
| 0.80.3 | 2 / 2 | |
| 0.80.2 | 2 / 2 | |
| 0.80.1 | 2 / 2 | |
| 0.79.10 | 2 / 2 | |
| 0.79.9 | 2 / 2 | |
| 0.79.8 | 2 / 2 | |
| 0.79.7 | 2 / 2 | |
| 0.79.6 | 2 / 2 | |
| 0.79.5 | 2 / 2 | |
| 0.79.4 | 2 / 2 | |
| 0.79.3 | 2 / 2 | |
| 0.79.2 | 2 / 2 | |
| 0.79.1 | 2 / 2 | |
| 0.79.0 | 2 / 2 | |
| 0.78.1 | 2 / 2 | |
| 0.78.0 | 2 / 2 | |
| 0.77.0 | 2 / 2 | |
| 0.76.0 | 2 / 2 | |
| 0.75.5 | 2 / 3 | |
| 0.75.4 | 2 / 3 | |
| 0.75.3 | 2 / 3 | |
| 0.75.2 | 2 / 3 | |
| 0.75.1 | 2 / 3 | |
| 0.75.0 | 2 / 3 | |
| 0.74.2 | 2 / 3 | |
| 0.74.1 | 2 / 3 | |
| 0.74.0 | 5 / 2 |
v0.82.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.82.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.81.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.81.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.80.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.80.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.80.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.80.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.80.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.80.5
2 findingsThis version was published by a different npm account than previous versions on 2026-07-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.80.3
2 findingsThis version was published by a different npm account than previous versions on 2026-06-30. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.