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

adamchainz / django-mysql

:dolphin: :horse: Extensions to Django for use with MySQL/MariaDB

PythonMIT★ 587 stars⑂ 114 forkssince Feb 2015View on GitHub ↗
KindLibraryNetwork servicehow this is determined

adamchainz/django-mysql holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (94/100) and lowest on Sustainability & Governance (66/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

90
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.

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

Ownership

Adam JohnsonPersonal account
3,968 followers1,357 public repossince Jun 2011@django, @djangolondon

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
PyPIdjango-mysql4.19.0702,15276359 days agodjangomariadbmysql

Metrics by category

Vitality

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

71Good · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
18.7/36Commit cadence — 27/52 weeks with commits
15.6/18Commit volume — 54 commits in the last year
10/10OpenSSF Scorecard: Maintained — 20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year54
human_commit_share0.74
days_since_last_push4
active_weeks_last_year27
How it's scored
16.2/27Ships releases — 98 version tags (no GitHub releases)
16.2/36Release recency — latest release 359 days ago
19.8/27Release cadence — a release every ~91.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count98
latest_release_tag4.19.0
releases_from_tagsyes
days_since_latest_release359
mean_days_between_releases91.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?

81Excellent · 17% of overall
How it's scored
44.9/60Stars — 587 stars
17.1/25Forks — 114 forks
5.3/15Watchers — 10 watchers
Inputs used
forks114
stars587
watchers10
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
78/80Monthly downloads — 702,152 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesdjango-mysql
dependents—
ecosystemspypi
total_downloads—
monthly_downloads702,152
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?

66Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.1/22.5Commit distribution — top contributor authored 95% of commits
13.5/13.5Contributor breadth — 24 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled24
top_contributor_share0.951
How it's scored
39/42Issue resolution — 93% of issues closed
27.5/30PR acceptance — 891/972 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/25 approved changesets -- score normalized to 0
Inputs used
merged_prs891
open_issues17
closed_issues222
prs_merged_7d0
prs_decided_7d0
prs_merged_30d8
prs_decided_30d8
issue_closed_ratio0.929
closed_unmerged_prs81
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
25/25Owner reach — 3,968 followers of adamchainz
25/25Track record — 1,357 public repos, account ~15 yr old
Inputs used
followers3,968
owner_typeUser
is_verified—
owner_loginadamchainz
public_repos1,357
account_age_days5,566
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
26/35Publish recency — latest publish 359 days ago
20/20Version history — 76 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesdjango-mysql
ecosystemspypi
any_deprecatedno
min_days_since_publish359

Engineering Quality

Are baseline engineering and documentation practices in place?

94Exceptional · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff]), tox.ini
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 26 out of 29 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://django-mysql.readthedocs.io/
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicsdjango, mysql, mariadb, python
has_wikino
homepagehttps://django-mysql.readthedocs.io/
docs_sitehttps://django-mysql.readthedocs.io/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

74Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2/2.5CI-Tests — 26 out of 29 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/25 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 5 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.8
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages3
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:django-mysql@4.19.0 runtime dependency closure — what installing the published package pulls in — 3 packages. Reachability is not analyzed.

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.

72Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 62 of 74 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.838
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff]), tox.ini
11/11Static type checking — src/django_mysql/py.typed
10/10Reproducible environment — lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 7 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/django_mysql/py.typed
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0.07
How it's scored
27/45Type-checkable code — Python with type-check config (src/django_mysql/py.typed)
55/55Manageable file sizes — 0/96 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes50,807
source_files_sampled96
oversized_source_files0

Key facts

587GitHub stars
24contributors
54commits, last 12 months
4days since last push
98releases
1bus factor
17open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi download statistics for 'django-mysql' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced
  • pypi download figures for django-mysql carried forward from the previous scan (stats endpoint unavailable this scan)

More detail

Star and fork history 0 ★ / 114 ⇿
0Stars
114Forks
98Releases

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.

02040608010012011242015-032020-072025-11
Major 7Minor 55Patch 36

Each point covers 10 days.

OpenSSF Scorecard 6.8 / 10
6.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-13 02:13 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
8CI-Tests26 out of 29 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/25 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPIdjango>=5.2pyproject.toml
All dependencies 57

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

RegistryPackageVersionRelation
PyPIdjango5.2.17direct
PyPIdjango6.0.8direct
PyPIdjango6.1direct
PyPIaccessible-pygments0.0.5indirect
PyPIalabaster1.0.0indirect
PyPIasgiref3.12.1indirect
PyPIbabel2.18.0indirect
PyPIbeautifulsoup44.15.0indirect
PyPIcertifi2026.7.22indirect
PyPIcharset-normalizer3.5.1indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.15.4indirect
PyPIdjango-jsonfield-backport1.0.5indirect
PyPIdjango-mysql4.19.0indirect
PyPIdocutils0.21.2indirect
PyPIdocutils0.22.4indirect
PyPIexceptiongroup1.3.1indirect
PyPIflake87.3.0indirect
PyPIfuro2025.12.19indirect
PyPIidna3.19indirect
PyPIimagesize2.0.0indirect
PyPIiniconfig2.3.0indirect
PyPIjinja23.1.6indirect
PyPImariadb-dyncol3.6.1indirect
PyPImarkupsafe3.0.3indirect
PyPImccabe0.7.0indirect
PyPImysqlclient2.2.8indirect
PyPIpackaging26.3indirect
PyPIpluggy1.6.0indirect
PyPIpycodestyle2.14.0indirect
PyPIpyflakes3.4.0indirect
PyPIpygments2.21.0indirect
PyPIpytest9.1.1indirect
PyPIpytest-django4.14.0indirect
PyPIpytest-flake8-path1.7.0indirect
PyPIpytest-randomly4.1.0indirect
PyPIrequests2.34.2indirect
PyPIroman-numerals4.1.0indirect
PyPIsnowballstemmer3.1.1indirect
PyPIsoupsieve2.9.2indirect
PyPIsphinx8.1.3indirect
PyPIsphinx9.0.4indirect
PyPIsphinx9.1.0indirect
PyPIsphinx-basic-ng1.0.0b2indirect
PyPIsphinx-copybutton0.5.2indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPIsqlparse0.6.0indirect
PyPItomli2.4.1indirect
PyPItyping-extensions4.16.0indirect
PyPItzdata2026.3indirect
PyPIunittest-parametrize1.8.0indirect
PyPIurllib32.7.0indirect
Dependency advisories 0

Installing pypi:django-mysql@4.19.0 pulls in 3 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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 statistics — PyPI.