@clidey/whodb-cli-linux-x64
WhoDB CLI server binary for Linux x64
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI with SLSA attestation is a legitimate and improved supply chain practice. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific binary packages legitimately have no deps, no keywords, and tiny payload — this is the expected structure. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.113.0 | 0 / 0 | |
| 0.112.0 | 0 / 0 | |
| 0.111.0 | 0 / 0 | |
| 0.110.0 | 0 / 0 | |
| 0.109.0 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v0.113.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.112.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.111.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.110.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-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.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.