Open-source Bash runtime
BashloomWeave better shell scripts.
An open-source, dependency-free Bash runtime and library for reliable scripts, system automation and terminal interfaces with graceful CI and non-TTY degradation.
The public v0.1.0-rc1 baseline is frozen for multi-consumer field validation. It is a prerelease, not a stable v0.1.0 release.
What it is
A small runtime layer for serious shell applications
Bashloom groups reliability primitives, validation, filesystem helpers and terminal UX behind a coherent Bash API without turning optional integrations into mandatory core dependencies.
Exact failure semantics
Command execution, retry, wait, cleanup and rollback-oriented helpers preserve failures instead of hiding them behind presentation logic.
Source-safe design
Loading the runtime is designed not to silently mutate the caller’s shell options, traps or global environment.
Terminal UX that degrades
Human, plain and CI-oriented output remains usable across TTY, pipes, TERM=dumb, NO_COLOR and constrained Unicode environments.
Modular consumption
Consumers can vendor a pinned release bundle, verify SHA-256 integrity offline and expose the runtime through one project-local adapter.
Consumption model
Pin the runtime. Verify it. Adapt it once.
The recommended repository integration treats Bashloom as a reviewed dependency rather than a floating script download.
- 01
Pin an official release bundle to an explicit version.
- 02
Keep PIN, LICENSE, SHA256SUMS and the complete runtime together.
- 03
Verify integrity before use and perform repins through an explicit reviewed update.
- 04
Expose Bashloom to the host project through one local adapter and validate it in CI.
Public state
RC baseline available for real consumer validation
The site records the last verified public baseline and links GitHub Releases as the authoritative place to check subsequent releases. It does not present the RC as stable.
- Verified baseline
- v0.1.0-rc1
- Channel
- RC / prerelease
- License
- MIT License
- Source
- Public repository
Engineering evidence
The implementation story is documented separately
The project case study focuses on API design, exact exit-status semantics, idempotency, terminal degradation, testing, release engineering and open-source governance.