@hashgraph/solo
An opinionated CLI tool to deploy and manage private Hedera Networks.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer roster change on a long-lived trusted org package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Guarded, best-effort image-cache prefetch only on global installs; skippable via SOLO_NO_CACHE. | ai | |
| phantom-deps | phantom-dep:enquirer | AI (phantom-deps): Declared dependency used for interactive CLI prompts; stable false positive. | ai | |
| phantom-deps | phantom-dep:inquirer | AI (phantom-deps): Declared dependency used for interactive CLI prompts; stable false positive. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Declared dependency used for YAML config parsing; stable false positive. | ai | |
| provenance | publisher-changed | AI (provenance): CI/CD migration with SLSA attestation, improved provenance direction. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Logging utility referenced in config; stable pattern for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Actively developed CLI tool; incremental source file additions are expected across frequent releases. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Active Hashgraph tooling package; new proto dependency is consistent with ledger protocol evolution, no malicious indicators. | ai | |
| dependencies | unvetted-dep:tsyringe-neo | AI (dependencies): tsyringe-neo was removed as a runtime dep in this version; finding is stale. | ai | |
| dependencies | unvetted-dep:elliptic | AI (dependencies): elliptic was removed as a runtime dep in this version; finding is stale. | ai | |
| dependencies | unvetted-dep:stream-buffers | AI (dependencies): stream-buffers was removed as a runtime dep in this version; finding is stale. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is cosmetic given Sigstore-backed CI publish. | ai | |
| phantom-deps | phantom-dep:stream-buffers | AI (phantom-deps): Phantom dep heuristic false positive for this established toolchain package. | ai | |
| phantom-deps | phantom-dep:shell-quote | AI (phantom-deps): Phantom dep heuristic false positive for this established toolchain package. | ai | |
| phantom-deps | phantom-dep:elliptic | AI (phantom-deps): Phantom dep heuristic false positive for this established toolchain package. | ai | |
| phantom-deps | phantom-dep:figlet | AI (phantom-deps): Phantom dep heuristic false positive for this established toolchain package. | ai | |
| phantom-deps | phantom-dep:esm | AI (phantom-deps): Phantom dep heuristic false positive for this established toolchain package. | ai | |
| phantom-deps | phantom-dep:ip | AI (phantom-deps): Phantom dep heuristic false positive for this established toolchain package. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Pattern is used to pass augmented PATH to subprocesses; not credential exfiltration. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decoding Hedera network message content for display; no malicious payload pattern. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.82.0 | 36 / 57 | |
| 0.72.0 | 36 / 57 | |
| 0.71.0 | 35 / 57 | |
| 0.70.0 | 35 / 57 | |
| 0.69.0 | 35 / 57 | |
| 0.68.0 | 34 / 57 | |
| 0.67.0 | 34 / 57 | |
| 0.66.0 | 34 / 57 | |
| 0.65.0 | 34 / 57 | |
| 0.64.1 | 34 / 58 | |
| 0.58.0 | 34 / 61 | |
| 0.53.1 | 33 / 61 | |
| 0.49.0 | 33 / 61 | |
| 0.40.0 | 32 / 59 | |
| 0.31.4 | 27 / 50 | |
| 0.31.3 | 27 / 50 | |
| 0.31.2 | 27 / 50 | |
| 0.31.1 | 27 / 50 | |
| 0.31.0 | 25 / 19 | |
| 0.30.1 | 25 / 20 | |
| 0.30.0 | 25 / 20 | |
| 0.29.0 | 24 / 20 | |
| 0.28.1 | 25 / 20 | |
| 0.28.0 | 25 / 20 | |
| 0.27.0 | 25 / 19 | |
| 0.26.0 | 25 / 19 | |
| 0.25.0 | 25 / 19 |
v0.82.0
2 findingsScript: node scripts/postinstall.mjs
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.58.0
3 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (hedera-eng-automation) on 2026-02-25, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.