MDAnalysis is a Python library to analyze molecular dynamics simulations.
MDAnalysis/mdanalysis holds a health index of 94 out of 100, placing it in the Exceptional band. It scores highest on Community & Adoption (86/100) and lowest on AI Readiness (49/100). It was last updated today. 3 contributors account for most of its recent work.
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.
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 80 is calibrated to 94 on the published index scale (record calibration 2026-08-02).
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| PyPI | MDAnalysis | 2.10.0 | 206,770 | 47 | 276 days ago | pythonsciencechemistrybiophysicsmolecular-dynamicscomputational-chemistrymolecular-simulationanalysistrajectory-analysis |
| PyPI | MDAnalysisTests | 2.10.0 | 12,818 | 44 | 276 days ago | — |
Is the project alive — is code being written and are releases shipping?
| 36/36 | Push recency — last push 0 days ago |
| 24.9/36 | Commit cadence — 36/52 weeks with commits |
| 18/18 | Commit volume — 110 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10 |
| commits_last_year | 110 |
| human_commit_share | — |
| days_since_last_push | 0 |
| active_weeks_last_year | 36 |
| 27/27 | Ships releases — 33 releases published |
| 16.2/36 | Release recency — latest release 276 days ago |
| 19.8/27 | Release cadence — a release every ~115 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
| releases_count | 33 |
| latest_release_tag | package-2.10.0 |
| releases_from_tags | no |
| days_since_latest_release | 276 |
| mean_days_between_releases | 115 |
Does the project have users, downloads, attention, and a welcoming setup for contributors?
| 52/60 | Stars — 1,610 stars |
| 24.4/25 | Forks — 849 forks |
| 8.9/15 | Watchers — 41 watchers |
| forks | 849 |
| stars | 1,610 |
| watchers | 41 |
| growth_state | organic |
| growth_factor_pct | 100 |
| 22.5/22.5 | README |
| 16.9/22.5 | License — license file present, not a recognized license |
| 18/18 | CONTRIBUTING guide |
| 13.5/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 6.3/6.3 | PR template |
| has_readme | yes |
| has_license | yes |
| readme_badges | — |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | yes |
| readme_badge_services | — |
| has_pull_request_template | yes |
| 71.2/80 | Monthly downloads — 219,588 downloads/month across pypi |
| 0/20 | Registry dependents — not reported by this ecosystem |
| packages | MDAnalysis, MDAnalysisTests |
| dependents | — |
| ecosystems | pypi |
| total_downloads | — |
| monthly_downloads | 219,588 |
| unverified_packages_excluded | — |
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
| 36/54 | Bus factor — 3 contributor(s) cover half of all commits |
| 17.9/22.5 | Commit distribution — top contributor authored 21% of commits |
| 13.5/13.5 | Contributor breadth — 100 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 57 contributing companies or organizations |
| bus_factor | 3 |
| contributors_sampled | 100 |
| top_contributor_share | 0.206 |
| 34.4/42 | Issue resolution — 82% of issues closed |
| 24.4/30 | PR acceptance — 2,091/2,567 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 15/15 | OpenSSF Scorecard: Code-Review — all changesets reviewed |
| merged_prs | 2,091 |
| open_issues | 440 |
| closed_issues | 1,977 |
| prs_merged_7d | — |
| prs_decided_7d | — |
| prs_merged_30d | — |
| prs_decided_30d | — |
| issue_closed_ratio | 0.818 |
| closed_unmerged_prs | 476 |
| first_time_authors_30d | — |
| first_time_prs_merged_30d | — |
| first_time_prs_decided_30d | — |
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain — verified-domain status not read for this organization |
| 18.3/25 | Owner reach — 347 followers of MDAnalysis |
| 25/25 | Track record — 77 public repos, account ~11 yr old |
| followers | 347 |
| owner_type | Organization |
| is_verified | — |
| owner_login | MDAnalysis |
| public_repos | 77 |
| account_age_days | 4,148 |
| 25/25 | Published & resolvable — 2 package(s) on pypi |
| 26/35 | Publish recency — latest publish 276 days ago |
| 20/20 | Version history — 47 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
| packages | MDAnalysis, MDAnalysisTests |
| ecosystems | pypi |
| any_deprecated | no |
| min_days_since_publish | 276 |
Are baseline engineering and documentation practices in place?
| 24/24 | CI workflows — 5 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — .flake8, .pylintrc |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 20/20 | OpenSSF Scorecard: CI-Tests — 23 out of 23 merged PRs checked by a CI test -- score normalized to 10 |
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | yes |
| has_precommit_config | no |
| 30/30 | README |
| 0/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://mdanalysis.org |
| 10/10 | Repository description |
| 10/10 | Topics — 8 topics |
| 10/10 | Wiki |
| topics | molecular-dynamics, python, science, trajectory-analysis, molecular-simulation, molecular-dynamics-simulation, mdanalysis, computational-chemistry |
| has_wiki | yes |
| homepage | https://mdanalysis.org |
| docs_site | https://mdanalysis.org |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 2.5/2.5 | CI-Tests — 23 out of 23 merged PRs checked by a CI test -- score normalized to 10 |
| 0.5/2.5 | CII-Best-Practices — badge detected: InProgress |
| 7.5/7.5 | Code-Review — all changesets reviewed |
| 2.5/2.5 | Contributors — project has 57 contributing companies or organizations |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.2/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10 |
| 5/5 | Packaging — packaging workflow detected |
| 0/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
| 1/5 | SAST — SAST tool is not run on all commits -- score normalized to 2 |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 7.5/7.5 | Vulnerabilities — 0 existing vulnerabilities detected |
| source | openssf_scorecard |
| checks_evaluated | 16 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 2 |
| scorecard_aggregate | 6.8 |
| 35/35 | Direct dependencies free of known advisories — no direct dependency carries a known advisory |
| 25/25 | Indirect dependencies free of known advisories — no indirect dependency carries a known advisory |
| 0/40 | No advisories left outstanding — no advisory carries a publication date |
| source | osv |
| advisories | 0 |
| affected_packages | 0 |
| assessed_packages | 21 |
| unassessed_packages | 0 |
| affected_by_severity | none |
| direct_affected_packages | 0 |
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.
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 0/40 | Legible commit history — no data |
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | — |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
| 18/18 | One-command bootstrap — package/doc/sphinx/Makefile |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — .flake8, .pylintrc |
| 11/11 | Static type checking — mypy.ini |
| 0/10 | Reproducible environment |
| 0/10 | Demonstrated agent practice — no data |
| 5/8 | Automated maintenance — dependency automation configured, none observed in the sampled commits |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | no |
| typed_language | no |
| bootstrap_files | package/doc/sphinx/Makefile |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | mypy.ini |
| agent_commit_share | — |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0 |
| 27/45 | Type-checkable code — Python with type-check config (mypy.ini) |
| 52.7/55 | Manageable file sizes — 19/454 source files over 60KB |
| primary_language | Python |
| largest_source_bytes | 190,357 |
| source_files_sampled | 454 |
| oversized_source_files | 19 |
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.
Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.
Each point covers 5 days.
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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| n/a | Branch-Protection | internal 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 |
| 10 | CI-Tests | 23 out of 23 merged PRs checked by a CI test -- score normalized to 10 |
| 2 | CII-Best-Practices | badge detected: InProgress |
| 10 | Code-Review | all changesets reviewed |
| 10 | Contributors | project has 57 contributing companies or organizations |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 9 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10 |
| 10 | Packaging | packaging workflow detected |
| 0 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 0 |
| 2 | SAST | SAST tool is not run on all commits -- score normalized to 2 |
| 0 | Security-Policy | security policy file not detected |
| n/a | Signed-Releases | no releases found |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 10 | Vulnerabilities | 0 existing vulnerabilities detected |
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| PyPI | numpy | >=1.26.0 | package/pyproject.toml |
| PyPI | GridDataFormats | >=0.4.0 | package/pyproject.toml |
| PyPI | mmtf-python | >=1.0.0 | package/pyproject.toml |
| PyPI | joblib | >=0.12 | package/pyproject.toml |
| PyPI | scipy | >=1.5.0 | package/pyproject.toml |
| PyPI | matplotlib | >=1.5.1 | package/pyproject.toml |
| PyPI | tqdm | >=4.43.0 | package/pyproject.toml |
| PyPI | threadpoolctl | — | package/pyproject.toml |
| PyPI | packaging | — | package/pyproject.toml |
| PyPI | filelock | — | package/pyproject.toml |
| PyPI | mda-xdrlib | — | package/pyproject.toml |
Full resolved dependency set from the GitHub dependency graph: 11 direct and 26 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| PyPI | filelock | — | direct |
| PyPI | griddataformats | — | direct |
| PyPI | joblib | — | direct |
| PyPI | matplotlib | — | direct |
| PyPI | mda-xdrlib | — | direct |
| PyPI | mmtf-python | — | direct |
| PyPI | numpy | — | direct |
| PyPI | packaging | — | direct |
| PyPI | scipy | — | direct |
| PyPI | threadpoolctl | — | direct |
| PyPI | tqdm | — | direct |
| PyPI | biopython | — | indirect |
| PyPI | chemfiles | — | indirect |
| PyPI | codecov | — | indirect |
| PyPI | cython | — | indirect |
| PyPI | gsd | — | indirect |
| PyPI | h5py | — | indirect |
| PyPI | hypothesis | — | indirect |
| PyPI | imdclient | — | indirect |
| PyPI | mdanalysis | 2.11.0-dev0 | indirect |
| PyPI | mdanalysis-sphinx-theme | — | indirect |
| PyPI | mypy | 0.960 | indirect |
| PyPI | netcdf4 | — | indirect |
| PyPI | networkx | — | indirect |
| PyPI | parmed | — | indirect |
| PyPI | pooch | — | indirect |
| PyPI | pyedr | — | indirect |
| PyPI | pytest | — | indirect |
| PyPI | pytng | — | indirect |
| PyPI | rdkit | — | indirect |
| PyPI | scikit-learn | — | indirect |
| PyPI | seaborn | — | indirect |
| PyPI | setuptools | — | indirect |
| PyPI | sphinx | — | indirect |
| PyPI | sphinx-sitemap | — | indirect |
| PyPI | tidynamics | — | indirect |
| PyPI | typing-extensions | — | indirect |
Installing pypi:MDAnalysis@2.10.0 pulls in 21 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.
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.
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.17.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — PyPI.