Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-06 02:53 UTC

blackbeam / mysql_async

Asyncronous Rust Mysql driver based on Tokio.

RustApache-2.0★ 414 stars⑂ 150 forkssince Oct 2016View on GitHub ↗

blackbeam/mysql_async holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (84/100) and lowest on Security (48/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

71
overall / 100
Good

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.

71
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 63 is calibrated to 71 on the published index scale (record calibration 2026-08-02).

Ownership

Anatoly IPersonal account
117 followers55 public repossince Nov 2009Busy 😮‍💨

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iomysql_async0.37.1400,265754 days agoasyncasynchronousdatabasemysql

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
15.2/36Commit cadence22/52 weeks with commits
16.9/18Commit volume76 commits in the last year
10/10OpenSSF Scorecard: Maintained16 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year76
human_commit_share1
days_since_last_push4
active_weeks_last_year22
How it's scored
27/27Ships releases63 releases published
36/36Release recencylatest release 4 days ago
19.8/27Release cadencea release every ~99.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count63
latest_release_tagv0.37.1
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases99.6
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

66Good · 17% of overall
How it's scored
42.4/60Stars414 stars
18.1/25Forks150 forks
3.9/15Watchers6 watchers
Inputs used
forks150
stars414
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesdev.azure.com, shields.io
has_pull_request_templateno
How it's scored
74.7/80Monthly downloads400,265 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesmysql_async
dependents
ecosystemscrates
total_downloads7,251,005
monthly_downloads400,265
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?

68Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.3/22.5Commit distributiontop contributor authored 81% of commits
13.5/13.5Contributor breadth58 contributors
10/10OpenSSF Scorecard: Contributorsproject has 22 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled58
top_contributor_share0.811
How it's scored
36.5/42Issue resolution87% of issues closed
26.1/30PR acceptance172/198 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 8/13 approved changesets -- score normalized to 6
Inputs used
merged_prs172
open_issues25
closed_issues167
prs_merged_7d1
prs_decided_7d1
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.87
closed_unmerged_prs26
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
14.9/25Owner reach117 followers of blackbeam
24.7/25Track record55 public repos, account ~16 yr old
Inputs used
followers117
owner_typeUser
is_verified
owner_loginblackbeam
public_repos55
account_age_days6,133
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on crates
35/35Publish recencylatest publish 4 days ago
20/20Version history75 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmysql_async
ecosystemscrates
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests6 out of 9 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/mysql_async
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_sitehttps://docs.rs/mysql_async
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

48Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
1.5/2.5CI-Tests6 out of 9 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 8/13 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 22 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained16 commit(s) and 4 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
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.8
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
23.5/40Legible commit history44 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.44
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingRust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.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)
52.9/55Manageable file sizes2/53 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes100,897
source_files_sampled53
oversized_source_files2

Key facts

414GitHub stars
58contributors
76commits, last 12 months
4days since last push
63releases
1bus factor
25open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 150 ⇿
0Stars
150Forks
60Releases

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.

025507510012515013032017-052022-012026-09
Major 0Minor 26Patch 31

Each point covers 9 days.

OpenSSF Scorecard 4.8 / 10
4.8aggregate

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-09-06 02:53 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
6CI-Tests6 out of 9 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 8/13 approved changesets -- score normalized to 6
10Contributorsproject has 22 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained16 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 28
RegistryPackageVersion constraintManifest
crates.ioarc-swap1.9.2Cargo.toml
crates.iobytes1.4Cargo.toml
crates.iocrossbeam-queue0.3Cargo.toml
crates.iocrossbeam-utils0.8.21Cargo.toml
crates.ioflate21.0Cargo.toml
crates.iofutures-core0.3Cargo.toml
crates.iofutures-util0.3Cargo.toml
crates.iofutures-sink0.3Cargo.toml
crates.iokeyed_priority_queue0.4Cargo.toml
crates.iolru0.18Cargo.toml
crates.iomysql_common0.38.2Cargo.toml
crates.iopem3.0Cargo.toml
crates.iopercent-encoding2.1.0Cargo.toml
crates.iorand0.10Cargo.toml
crates.ioserde1Cargo.toml
crates.iosocket20.6Cargo.toml
crates.iothiserror2Cargo.toml
crates.iotokio1.0Cargo.toml
crates.iotokio-util0.7.2Cargo.toml
crates.iotracing0.1.37Cargo.toml
crates.iotwox-hash2Cargo.toml
crates.iourl2.1Cargo.toml
crates.iohdrhistogram7.5Cargo.toml
crates.iotokio-rustls0.26Cargo.toml
crates.iotokio-native-tls0.3.0Cargo.toml
crates.ionative-tls0.2Cargo.toml
crates.iorustls0.23.14Cargo.toml
crates.iowebpki-roots1Cargo.toml
All dependencies 30

Full resolved dependency set from the GitHub dependency graph: 28 direct and 2 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
crates.ioarc-swapdirect
crates.iobytesdirect
crates.iocrossbeam-queuedirect
crates.iocrossbeam-utilsdirect
crates.ioflate2direct
crates.iofutures-coredirect
crates.iofutures-sinkdirect
crates.iofutures-utildirect
crates.iohdrhistogramdirect
crates.iokeyed_priority_queuedirect
crates.iolrudirect
crates.iomysql_commondirect
crates.ionative-tlsdirect
crates.iopemdirect
crates.iopercent-encodingdirect
crates.ioranddirect
crates.iorustlsdirect
crates.ioserdedirect
crates.iosocket2direct
crates.iothiserrordirect
crates.iotokiodirect
crates.iotokio-native-tlsdirect
crates.iotokio-rustlsdirect
crates.iotokio-utildirect
crates.iotracingdirect
crates.iotwox-hashdirect
crates.iourldirect
crates.iowebpki-rootsdirect
crates.iotempfileindirect
crates.iowaker-fnindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.