bashrs-runtime 6.63.0

Table of Contents

• What's New
• Why Rash?
• Quick Start
• Features
• Core Commands
• Advanced Testing
• Documentation
• Quality Metrics
• Shell Compatibility
• Performance
• MCP Server
• Contributing
• License

🚀 What's New in v6.61.0

Latest Release - 2026-02-10

• Transpiler Bug Fixes: 2 critical correctness fixes
  • return inside while/for/match in functions now correctly emits shell arithmetic
  • let x = match y { ... } now generates proper case statements instead of x='unknown'
• Corpus Expansion: 14,712 transpilation entries (13,397 Bash + 695 Makefile + 620 Dockerfile)
  • V2 Score: 97.5/100 (A+), 0 failures across all entries
  • 107+ CLI subcommands for corpus analysis, quality gates, and convergence tracking
• New Example: transpiler_demo showcasing nested calls, match-in-let, recursion, and multi-function programs
• Quality Metrics: 10,888 tests, 97.5/100 corpus score (A+)

See CHANGELOG.md for complete release notes.

Why Rash?

Shell scripts are everywhere—CI/CD pipelines, deployment automation, system configuration—but they're notoriously difficult to write safely. Rash solves this by providing:

1. Bidirectional Safety: Write in Rust and transpile to shell, or purify existing bash scripts
2. Automatic Transformation: Don't just detect problems—fix them automatically
3. Deterministic Guarantees: Same input always produces identical, reproducible output
4. Zero Runtime Dependencies: Generated scripts run on any POSIX-compliant system

Features

• 🛡️ Automatic Safety: Protection against shell injection, word splitting, glob expansion
• 🔍 Beyond Linting: Full AST semantic understanding - transforms code, doesn't just warn
• 📦 Zero Runtime Dependencies: Generated scripts work on any POSIX shell
• 🎯 Deterministic Output: Same input always produces identical scripts
• ✅ ShellCheck Compliant: All output passes strict linting

How Rash Exceeds ShellCheck

Key Difference: ShellCheck tells you what's wrong. Rash understands your code's intent and rewrites it to be safe, deterministic, and idempotent — automatically.

Quick Start

Installation

# From crates.io (recommended)
cargo install bashrs

# Or from source
git clone https://github.com/paiml/bashrs
cd bashrs
cargo install --path rash

Write Rust, Get Safe Shell

// install.rs
#[rash::main]
fn main() {
    let version = env_var_or("VERSION", "1.0.0");
    let prefix = env_var_or("PREFIX", "/usr/local");

    echo("Installing MyApp {version} to {prefix}");

    mkdir_p("{prefix}/bin");
    mkdir_p("{prefix}/share/myapp");

    if exec("cp myapp {prefix}/bin/") {
        echo("✓ Binary installed");
    } else {
        eprint("✗ Failed to install binary");
        exit(1);
    }
}

Transpile to safe POSIX shell:

$ bashrs build install.rs -o install.sh

Or Purify Existing Bash

Before (messy bash):

#!/bin/bash
SESSION_ID=$RANDOM                      # Non-deterministic
mkdir /app/releases/$RELEASE            # Non-idempotent
rm /app/current                         # Fails if doesn't exist

After (purified by Rash):

#!/bin/sh
session_id="session-${version}"         # ✅ Deterministic
mkdir -p "/app/releases/${release}"     # ✅ Idempotent
rm -f "/app/current"                    # ✅ Safe removal

Core Commands

# Transpile Rust to shell
bashrs build input.rs -o output.sh

# Purify legacy bash scripts
bashrs purify messy.sh -o clean.sh

# Interactive REPL with debugging
bashrs repl

# Lint shell scripts (including Dockerfiles)
bashrs lint script.sh

# Test bash scripts
bashrs test script.sh

# Quality scoring
bashrs score script.sh

# Comprehensive audit
bashrs audit script.sh

Advanced Testing

Rash includes Probar integration for comprehensive quality assurance:

# State machine testing with playbooks
bashrs playbook install.playbook.yaml --run

# Mutation testing (goal: >90% kill rate)
bashrs mutate script.sh --count 10

# Deterministic simulation replay
bashrs simulate script.sh --seed 42 --verify

Mutation Operators: Rash applies 10 mutation operators including string mutations, command substitutions, conditional inversions, and redirect modifications to verify test quality.

📚 Documentation

The Rash Book is the canonical source for all documentation:

→ Read The Rash Book

Quick links:

• Getting Started
• Quick Start Tutorial
• Linting Rules
• Configuration Management
• API Reference

Why the book?

• ✅ All examples automatically tested
• ✅ Always up-to-date with latest release
• ✅ Comprehensive coverage of all features
• ✅ Real-world examples and tutorials

Quality Metrics

Falsification Testing (Popper Methodology)

Rash uses Popperian falsification—tests attempt to disprove functionality rather than prove it works:

# Run 130-point transpiler falsification checklist
cargo test -p bashrs --test transpiler_tcode_tests

# Run 30-point Dockerfile falsification checklist
cargo test -p bashrs --test dockerfile_dcode_tests

A passing test means the falsification attempt failed—the feature works correctly.

Shell Compatibility

Generated scripts are tested on:

Performance

Rash is designed for fast transpilation:

• Rust-to-Shell: 21.1µs transpile time
• Makefile Parsing: 0.034-1.43ms (70-320x faster than targets)
• Memory Usage: <10MB for most scripts

MCP Server

Rash provides a Model Context Protocol (MCP) server for AI-assisted shell script generation:

# Install MCP server
cargo install rash-mcp

# Run server
rash-mcp

Available in the official MCP registry as io.github.paiml/rash.

Contributing

We welcome contributions! See our Contributing Guide for details.

# Clone and test
git clone https://github.com/paiml/bashrs.git
cd bashrs
make test

# Run all quality checks
make validate

License

MIT License. See LICENSE for details.