Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 09:52 UTC

paiml / bashrs

Bashrs: Rust-to-Shell Transpiler for Deterministic Bootstrap Scripts

RustMIT★ 37 stars⑂ 3 forkssince May 2025View on GitHub ↗
KindCommand-line toolLibraryTerminal interfacehow this is determined

paiml/bashrs holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (100/100) and lowest on Community & Adoption (52/100). It was last updated today. A single contributor accounts for most of its recent work.

87
overall / 100
Excellent

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

87
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 73 is calibrated to 87 on the published index scale (record calibration 2026-08-02).

Ownership

Pragmatic AI LabsOrganization
331 followers193 public repossince Nov 2016

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

88Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
21.5/36Commit cadence31/52 weeks with commits
18/18Commit volume1,739 commits in the last year
10/10OpenSSF Scorecard: Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,739
human_commit_share1
days_since_last_push0
active_weeks_last_year31
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~22.1 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagnightly
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases22.1

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

52Moderate · 17% of overall
How it's scored
25.2/60Stars37 stars
2.5/25Forks3 forks
0/15Watchers0 watchers
Inputs used
forks3
stars37
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
45.9/80Monthly downloads2,779 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesbashrs, rash-mcp, bashrs-runtime, bashrs-oracle
dependents
ecosystemscrates
total_downloads32,263
monthly_downloads2,779
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

62Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1/22.5Commit distributiontop contributor authored 96% of commits
2.7/13.5Contributor breadth2 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.955
How it's scored
35.7/42Issue resolution85% of issues closed
27.1/30PR acceptance74/82 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs74
open_issues25
closed_issues141
prs_merged_7d5
prs_decided_7d5
prs_merged_30d14
prs_decided_30d15
issue_closed_ratio0.849
closed_unmerged_prs8
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
18.1/25Owner reach331 followers of paiml
25/25Track record193 public repos, account ~9 yr old
Inputs used
followers331
owner_typeOrganization
is_verifiedno
owner_loginpaiml
public_repos193
account_age_days3,567

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable4 package(s) on crates
35/35Publish recencylatest publish 6 days ago
20/20Version history109 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesbashrs, rash-mcp, bashrs-runtime, bashrs-oracle
ecosystemscrates
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

100Exceptional · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
16/16Linter config.clippy.toml, Cargo.toml ([lints], [workspace.lints]), bashrs-oracle/Cargo.toml ([lints]), rash-mcp/Cargo.toml ([lints]), rash-runtime/Cargo.toml ([lints]), rash/Cargo.toml ([lints]), rustfmt.toml
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests21 out of 21 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://paiml.github.io/bashrs/
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsbash, mcp, rust, paiml-active-tool
has_wikiyes
homepagehttps://paiml.github.io/bashrs/
docs_sitehttps://paiml.github.io/bashrs/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

57Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests21 out of 21 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
5/5Fuzzingproject is fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
2/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.7
Excluded from scoring (no data or not applicable): Packaging, Pinned-Dependencies. Remaining weights renormalized.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

94Exceptional · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes34,312
How it's scored
18/18One-command bootstrapMakefile, justfile
22/22Automated tests
11/11Lint / format config.clippy.toml, Cargo.toml ([lints], [workspace.lints]), bashrs-oracle/Cargo.toml ([lints]), rash-mcp/Cargo.toml ([lints]), rash-runtime/Cargo.toml ([lints]), rash/Cargo.toml ([lints]), rustfmt.toml
11/11Static type checkingRust (statically typed)
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice89 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile, justfile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.89
toolchain_manifestsCargo.toml, bashrs-oracle/Cargo.toml, bashrs-wasm/Cargo.toml, fuzz/Cargo.toml, rash-mcp/Cargo.toml, rash-runtime/Cargo.toml, rash/Cargo.toml
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeRust (statically typed)
55/55Manageable file sizes0/2,038 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes40,972
source_files_sampled2,038
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

37GitHub stars
2contributors
1,739commits, last 12 months
0days since last push
100releases
1bus factor
25open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'bashrs-specs' from its registry
  • Could not fetch crates package 'bashrs-wasm' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 3 ⇿
0Stars
3Forks
12Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

12233312026-012026-032026-05
Major 0Minor 11Patch 1
OpenSSF Scorecard 5.7 / 10
5.7aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-28 09:52 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests21 out of 21 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesinternal error: internal error: invalid Dockerfile: Syntax error - can't find = in "+%Y%m%d)". Must be of the form: name=value
0SASTSAST tool is not run on all commits -- score normalized to 0
4Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 62
RegistryPackageVersion constraintManifest
crates.iobashrs6.67.0Cargo.toml
crates.ioaprender0.26bashrs-oracle/Cargo.toml
crates.ioserdebashrs-oracle/Cargo.toml
crates.ioserde_jsonbashrs-oracle/Cargo.toml
crates.iothiserrorbashrs-oracle/Cargo.toml
crates.ioanyhow1.0bashrs-oracle/Cargo.toml
crates.iotracingbashrs-oracle/Cargo.toml
crates.ioregex1.11bashrs-oracle/Cargo.toml
crates.iobashrs6.67.0bashrs-wasm/Cargo.toml
crates.iowasm-bindgen0.2bashrs-wasm/Cargo.toml
crates.ioserde1bashrs-wasm/Cargo.toml
crates.ioserde_json1bashrs-wasm/Cargo.toml
crates.iosafetensors0.4bashrs-wasm/Cargo.toml
crates.iobashrs6.67rash-mcp/Cargo.toml
crates.iopforge-runtime0.1.4rash-mcp/Cargo.toml
crates.ioserderash-mcp/Cargo.toml
crates.ioserde_jsonrash-mcp/Cargo.toml
crates.iotokiorash-mcp/Cargo.toml
crates.ioanyhowrash-mcp/Cargo.toml
crates.iothiserrorrash-mcp/Cargo.toml
crates.ioschemars0.8rash-mcp/Cargo.toml
crates.ioasync-trait0.1rash-mcp/Cargo.toml
crates.iotoml0.8rash-mcp/Cargo.toml
crates.iosynrash/Cargo.toml
crates.ioquoterash/Cargo.toml
crates.ioproc-macro2rash/Cargo.toml
crates.ioserderash/Cargo.toml
crates.ioserde_jsonrash/Cargo.toml
crates.iotoml0.8rash/Cargo.toml
crates.ioanyhowrash/Cargo.toml
crates.iothiserrorrash/Cargo.toml
crates.ioclaprash/Cargo.toml
crates.iotokiorash/Cargo.toml
crates.iotracingrash/Cargo.toml
crates.iotracing-subscriberrash/Cargo.toml
crates.ioblake3rash/Cargo.toml
crates.ioonce_cellrash/Cargo.toml
crates.iolazy_staticrash/Cargo.toml
crates.iophfrash/Cargo.toml
crates.iochrono0.4rash/Cargo.toml
crates.iorand0.9rash/Cargo.toml
crates.iorand_chacha0.9rash/Cargo.toml
crates.iobatuta-common0.1rash/Cargo.toml
crates.iostatic_assertions1.1rash/Cargo.toml
crates.iorayon1.10rash/Cargo.toml
crates.ioregex1.10rash/Cargo.toml
crates.ioglob0.3rash/Cargo.toml
crates.iorustylinerash/Cargo.toml
crates.iosysinfo0.31rash/Cargo.toml
crates.ioschemars0.8rash/Cargo.toml
crates.iobashrs-oracle6.60rash/Cargo.toml
crates.ioaprender0.27rash/Cargo.toml
crates.ioentrenar0.7rash/Cargo.toml
crates.ionotify7.0rash/Cargo.toml
crates.ionotify-debouncer-mini0.5rash/Cargo.toml
crates.iotower-lsp0.20rash/Cargo.toml
crates.iozstd0.13rash/Cargo.toml
crates.iotar0.4rash/Cargo.toml
crates.ioflate21.1rash/Cargo.toml
crates.iobase640.22rash/Cargo.toml
crates.ioratatui0.29rash/Cargo.toml
crates.iocrossterm0.28rash/Cargo.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticscrates.io.