Basis CLI

Only the latest release is supported, and there is a documented upgrade path that is a single command: re-running ./download.sh fetches and verifies the newest version this repository knows about, because the version is resolved from checksums/ by version sort rather than pinned. SECURITY.md states the support policy and why — this tracks a development network that may be reset without notice, so pinning an old client to a chain that no longer exists helps nobody — and the roadmap repeats it as a deliberate non-goal rather than an omission. The upgrade is not difficult: there is no state to migrate, no configuration file, and no installed footprint beyond the binary itself. The CHANGELOG records what changed between versions and what it means.

GitHub Issues. https://github.com/basis-network/basis-cli/issues

No vulnerabilities have been reported or resolved in this repository in the last 12 months — the repository has existed since August 2026 and has had no vulnerability reports at all, so there is nobody to credit yet. The policy for when there is one is already written rather than improvised at the time: SECURITY.md states that reporters are credited in the release notes unless they ask not to be, and the documented handling process ends with the advisory published, the CHANGELOG saying what changed and why, and the reporter credited. https://github.com/basis-network/basis-cli/blob/main/SECURITY.md#reporting-a-vulnerability

SECURITY.md documents the process end to end in six steps: acknowledge the reporter and open a GitHub private security advisory (so an emailed report ends up in the same place, visible to the reporter); triage — reproduce, and decide whether it falls inside this repository's security boundary or belongs to basis-core or the network, forwarding it and saying where it went if it does not; record severity, scope and affected versions in the advisory; fix on a branch with a regression test where the defect is testable from here, reviewed before merge; release, with checksums committed before publication and assets verified and signed by the release workflow; disclose, with the advisory published, the CHANGELOG explaining the change and the reporter credited, timing agreed with them. A report that turns out not to be a vulnerability gets told why rather than left waiting. Committed timelines: acknowledgement within 3 working days, first assessment within 10, a fix or a stated plan within 90 days. https://github.com/basis-network/basis-cli/blob/main/SECURITY.md#how-a-report-is-handled

The primary language is bash, and CONTRIBUTING.md names the Google Shell Style Guide as the standard contributions follow, with two deliberate differences stated rather than left to be discovered: comments explain why and not what, and indentation is two spaces to match the existing scripts. It also states the conventions for the other file types here — YAML workflows two-space indented with every action pinned to a commit SHA, Markdown wrapped at 80 columns — and requires that a silenced lint rule carries a # shellcheck disable= directive at the line it applies to with a reason, never file-wide. https://github.com/basis-network/basis-cli/blob/main/CONTRIBUTING.md#coding-style

shellcheck is the FLOSS tool for this language and it runs in CI on every push and every pull request, over download.sh, test/run.sh and test/coverage.sh. It is a required status check on the protected main branch, so a violation blocks the merge rather than producing a warning somebody may or may not read; the same command is available locally as make lint. Exceptions are allowed but must be per-line # shellcheck disable= directives with a reason at the point they apply, so they are reviewable and can be handled automatically later. There are currently none: the tree is clean with no suppressions at all.

No native binaries are generated by this project. There is no compiler and no linker involved anywhere in this repository: the software it produces is bash read by an interpreter as it is, and the Makefile has no build target — only check, coverage and lint. The compiled basis binary is built elsewhere, from basis-core, which is outside this entry's declared scope. There are therefore no CC, CFLAGS, CXX, CXXFLAGS or LDFLAGS for anything here to honour or override.

There is no build or installation system that could strip anything. Nothing is compiled, so no debugging information is generated in the first place, and download.sh copies bytes and verifies a digest rather than installing with install -s or anything like it. The script it produces is its own source and is fully readable at run time.

There is no build system to be recursive. The Makefile is flat, has no build target, no subdirectory makefiles and no cross-directory dependencies: each target is a single command that runs a script in place. Nothing is compiled, so there is no dependency graph that could be got wrong.

No building occurs. This is a scripting-language project: download.sh and test/run.sh are used directly by the interpreter, not compiled into anything, so there is no generated artefact whose bit-for-bit reproduction could be compared. Reproducibility of the compiled binary is a property of basis-core, outside this entry's scope, and is listed as a known gap in the assurance case rather than claimed here.

Installation is ./download.sh, which is the commonly-used convention for this kind of tool — a single verified-download script, the same pattern as rustup or the many curl | sh installers, except that this one refuses to proceed if it cannot verify what it fetched. The README documents it as the first thing after the description, along with the by-hand curl plus sha256sum -c equivalent for readers who want to do it themselves. Uninstallation is equally simple and is a real answer rather than a dodge: everything the script produces lives under bin/<platform>/ inside the clone, nothing is written outside it, no system directory is touched, no service is registered and no configuration file is created anywhere. Deleting the directory removes the tool completely.

There is no installation system that writes outside its own directory, so there is no standard convention to honour. download.sh writes only to bin/<platform>/ relative to the script's own location; it installs nothing into a system prefix, so DESTDIR and PREFIX have nothing to select. Where the binary goes afterwards is the user's choice, made with mv or by adding that directory to PATH.

Clone the repository and run make check. That is the whole development environment: the suite needs nothing that download.sh itself does not need — bash, curl and a SHA-256 tool, all present on a stock Linux or macOS — and it touches no network, because each case fabricates a throwaway release in a temporary directory and reaches it over file://. There is nothing to install, no language runtime to provision, no container to build and no fixture to download. make lint adds shellcheck and reuse, and make coverage adds bashcov (gem install bashcov); both are documented in CONTRIBUTING.md and neither is needed to make and test a change.

This repository ships no code dependencies — no package manifest, no vendored code, nothing from a language registry — and the two classes of external dependency it does have are both listed in a computer-processable way. The GitHub Actions the workflows call are declared in the workflow YAML with every action pinned to a commit SHA and the version in a trailing comment, which is the convention for that ecosystem and is what Dependabot reads; .github/dependabot.yml declares the github-actions ecosystem so those declarations are watched weekly. The run-time dependencies are the operating system's own bash, curl and sha256sum or shasum, which is why there is no manifest to add them to; the README and CONTRIBUTING.md both state them, and the script itself checks for the SHA-256 tool at run time and exits if it is missing. https://github.com/basis-network/basis-cli/blob/main/.github/dependabot.yml

Dependabot runs weekly over the github-actions ecosystem and opens a pull request when a pinned action moves, which is the whole point of the configuration: pinning to a commit SHA makes an action safe but not current, and without something watching, a pin quietly rots. Six such updates have already been merged. Those pull requests run the same required CI as any other change, so an update cannot land broken. GitHub's own vulnerability alerting is enabled on the repository, CodeQL analyses the workflows on every push and weekly, and OpenSSF Scorecard publishes a Vulnerabilities check result publicly on every push. There are no other external components: no language-registry dependencies and no convenience copies of anything.

Everything reused is the standard component provided by the system. The script uses the operating system's bash, curl and sha256sum or shasum, all updated by the system package manager, and there are no convenience copies, no vendored libraries and no forked standard components anywhere in the tree — so a security update to any of them takes effect immediately, with nothing here holding an old copy alive. The only other reused components are the GitHub Actions, which are pinned by commit SHA and therefore trivially identifiable, and Dependabot updates them weekly.

Nothing deprecated or obsolete is used. The script's entire external surface is POSIX-standard utilities and current curl options, with no shell builtin or flag that has been deprecated; shellcheck runs in CI specifically to catch constructs that are obsolete or fragile, and the tree is clean with no suppressions. The CI side is kept current by Dependabot: all GitHub Actions are on their current major versions, and when a whole family had to move together — every codeql-action reference from v3 to v4 — it was done in a single change rather than left half-migrated.

.github/workflows/test.yml runs the full suite on every push to main and every pull request targeting it, via make check. It reports success or failure as a GitHub status check — download.sh test suite — which is required on the protected branch, so a failing suite blocks the merge rather than being noticed later. The suite is nine cases and 28 assertions covering the whole download-and-verify path end to end, including the two failure paths that justify the repository. A second job in the same workflow measures statement coverage and fails below 90%.

No bugs have been fixed in this repository in the last six months, so there is no denominator: the repository was made public in August 2026, has had no bug reports against download.sh and no defect fixes to add regression tests for. The policy for when there is one is already in place rather than to be decided later — CONTRIBUTING.md requires that a change to what download.sh does comes with a test, the review checklist makes a behaviour change without a test a blocking comment, and SECURITY.md's handling process specifies a regression test as part of fixing a reported vulnerability. Two of the nine existing cases are failure paths written for exactly this purpose.

Measured, not estimated: 98.1% statement coverage of download.sh, 52 of 53 statements. make coverage runs the suite under bashcov, the FLOSS coverage tool for bash, and CI runs it as its own job on every push and every pull request, failing the job below a hard floor of 90% — so a regression shows up as a red check on the pull request that caused it. Getting an honest figure needed two things that are documented in test/coverage.sh: the suite deletes each sandbox when its case ends, taking the traced copy of the script with it, so BASIS_TEST_KEEP keeps them; and SimpleCov silently drops any path with a dot-prefixed component, which yields a confident 0% with no error. Each case traces its own copy of the same bytes, so the copies are summed per line. One line is reported uncovered and is not — the done carrying the loop's redirection, which bash attributes to the while — and it is left in the report rather than special-cased, because a coverage tool taught to lie about one line stops being evidence about the others.

CONTRIBUTING.md states it as a rule, not a suggestion: "A change to what download.sh does comes with a test." It goes on to say why, which is what makes it stick — the script exists to refuse a download that does not match the committed checksum, and a refusal that stops working is silent. The same document requires make check to pass and asks contributors to say in the pull request which case covers their change, and the review checklist makes a behaviour change with no covering test a blocking comment. SECURITY.md applies the same rule to vulnerability fixes.

It is written down in CONTRIBUTING.md, in the section a contributor reads before opening a pull request, and repeated as a checklist item in the pull request template. https://github.com/basis-network/basis-cli/blob/main/CONTRIBUTING.md#tests

shellcheck runs at its default severity, which is the lowest one and therefore reports everything from style upwards, over every script in the repository, with no exclusions and no suppressions. Its optional --enable=all checks were reviewed and not adopted: they are formatting preferences (brace every variable reference, prefer [[ ]] to [ ]) rather than defect detection, and adopting them would mean rewriting working code to a house style it does not use.

docs/ASSURANCE-CASE.md works through Saltzer and Schroeder principle by principle with the concrete application in each row. The ones that carry the design: fail-safe defaults — every path denies by default, and no checksum file, no hash tool or a digest mismatch each end in a non-zero exit with the binary never made executable; separation of privilege — subverting a download requires control of both the release and the git history, two mechanisms with different failure modes and different audiences; economy of mechanism — about 110 lines of bash, no dependency manifest, no configuration file and no persistent state, so the whole verification argument fits on a page; complete mediation — every name in the checksum file is verified, not just the first, which the multi-entry test case guards; least privilege — workflows are read-all by default and elevated per job only where genuinely needed. Where principles conflict the choice is stated rather than hidden.