Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-15 12:15 UTC

Ruibin-Liu / pdbx2df

Super lightweight and fast mmCIF/PDB/MOL2 file parser into Pandas DataFrames and backwards writer.

PythonMIT★ 11 stars⑂ 2 forkssince Jan 2023View on GitHub ↗

Ruibin-Liu/pdbx2df holds a health index of 42 out of 100, placing it in the Weak band. It scores highest on Engineering Quality (95/100) and lowest on Security (1/100). It was last updated 99 days ago. A single contributor accounts for most of its recent work.

42
overall / 100
Weak

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.

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

Ownership

Ruibin LiuPersonal account
37 followers50 public repossince Apr 2014University of Maryland School of Pharmacy

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

Metrics by category

Vitality

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

31At Risk · 21% of overall
How it's scored
9.9/36Push recencylast push 99 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year0
human_commit_share
days_since_last_push99
active_weeks_last_year0
How it's scored
27/27Ships releases30 releases published
0/36Release recencylatest release 1,009 days ago
27/27Release cadencea release every ~2.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count30
latest_release_tagv0.7.5
releases_from_tagsno
days_since_latest_release1,009
mean_days_between_releases2.9

Community & Adoption

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

48Weak · 17% of overall
How it's scored
16.2/60Stars11 stars
0/25Forks2 forks
0/15Watchers2 watchers
Inputs used
forks2
stars11
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

43Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.6/22.5Commit distributiontop contributor authored 93% of commits
5.4/13.5Contributor breadth4 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.928
How it's scored
14/42Issue resolution33% of issues closed
29/30PR acceptance28/29 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs28
open_issues6
closed_issues3
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.333
closed_unmerged_prs1
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
11.4/25Owner reach37 followers of Ruibin-Liu
24.4/25Track record50 public repos, account ~12 yr old
Inputs used
followers37
owner_typeUser
is_verified
owner_loginRuibin-Liu
public_repos50
account_age_days4,464
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

95Exceptional · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configtox.ini
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://moldf.readthedocs.io/en/latest/
10/10Repository description
10/10Topics7 topics
10/10Wiki
Inputs used
topicsbioinformatics, pandas, pdb-parser, mmcif, mol2, python, atomselection
has_wikiyes
homepagehttps://moldf.readthedocs.io/en/latest/
docs_sitehttps://moldf.readthedocs.io/en/latest/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

1Critical · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles
manifestsdocs/requirements.txt, pyproject.toml, requirements.txt, requirements_dev.txt, setup.cfg, setup.py
has_codeql_workflowno
has_security_policyno
has_dependabot_configno

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.

55Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapdocs/Makefile
22/22Automated tests
11/11Lint / format configtox.ini
11/11Static type checkingmoldf/py.typed
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configsmoldf/py.typed
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
27/45Type-checkable codePython with type-check config (moldf/py.typed)
53.2/55Manageable file sizes1/30 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes61,107
source_files_sampled30
oversized_source_files1

Key facts

11GitHub stars
4contributors
0commits, last 12 months
99days since last push
30releases
1bus factor
6open issues
PyPIpackage ecosystems

Data collection warnings

  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

All dependencies 15

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

RegistryPackageVersionRelation
PyPIblackindirect
PyPIflake8indirect
PyPIfuroindirect
PyPIisortindirect
PyPImypyindirect
PyPInumpyindirect
PyPIpandasindirect
PyPIpre-commitindirect
PyPIpytestindirect
PyPIpytest-covindirect
PyPIscipyindirect
PyPIsphinxindirect
PyPIsphinx-copybuttonindirect
PyPItoxindirect
PyPItyping-extensionsindirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics.