Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 04:29 UTC

bigbio / qpx

qpx (Quantitative Proteomics eXchange) format (aka quantms.io) a format to capture a full proteomics experiment

PythonApache-2.0★ 26 stars⑂ 9 forkssince Apr 2023View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

bigbio/qpx holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (96/100) and lowest on Community & Adoption (48/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

BigBio StackOrganization
72 followers60 public repossince Feb 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIqpx1.1.6207105 days agobioinformatics-datamultiomicsparquetproteomicsproteomics-datapythonquantmsreanalysisstandardized-format

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 5 days ago
29.1/36Commit cadence — 42/52 weeks with commits
18/18Commit volume — 955 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year955
human_commit_share1
days_since_last_push5
active_weeks_last_year42

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 10 releases published
36/36Release recency — latest release 5 days ago
27/27Release cadence — a release every ~21.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count10
latest_release_tagv1.1.6
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases21.5
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?

48Weak · 17% of overall
How it's scored
22.7/60Stars — 26 stars
7.5/25Forks — 9 forks
4.7/15Watchers — 8 watchers
Inputs used
forks9
stars26
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesapp.codacy.com, badge.fury.io, github.com
has_pull_request_templateno
How it's scored
30.9/80Monthly downloads — 207 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesqpx
dependents—
ecosystemspypi
total_downloads—
monthly_downloads207
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?

73Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.8/22.5Commit distribution — top contributor authored 57% of commits
13.5/13.5Contributor breadth — 11 contributors
10/10OpenSSF Scorecard: Contributors — project has 8 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled11
top_contributor_share0.566
How it's scored
38.2/42Issue resolution — 91% of issues closed
28.1/30PR acceptance — 220/235 decided PRs merged
13/13Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs220
open_issues10
closed_issues100
prs_merged_7d5
prs_decided_7d5
prs_merged_30d12
prs_decided_30d12
issue_closed_ratio0.909
closed_unmerged_prs15
first_time_authors_30d1
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
13.4/25Owner reach — 72 followers of bigbio
25/25Track record — 60 public repos, account ~11 yr old
Inputs used
followers72
owner_typeOrganization
is_verifiedno
owner_loginbigbio
public_repos60
account_age_days4,272

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 5 days ago
20/20Version history — 10 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesqpx
ecosystemspypi
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
16/16Linter config — .pylintrc, pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 3 out of 3 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://qpx.quantms.org
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://qpx.quantms.org
docs_sitehttps://qpx.quantms.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

66Good · 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.5/2.5CI-Tests — 3 out of 3 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 8 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not 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_aggregate5.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_packages41
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:qpx@1.1.6 runtime dependency closure — what installing the published package pulls in — 41 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.

61Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt present
40/40Legible commit history — 95 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url—
legible_history_share0.95
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .pylintrc, pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile
10/10Demonstrated agent practice — 21 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.21
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
54.5/55Manageable file sizes — 2/240 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes65,225
source_files_sampled240
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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

26GitHub stars
11contributors
955commits, last 12 months
5days since last push
10releases
1bus factor
10open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 9 ⇿
0Stars
9Forks
9Releases

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.

0246810912024-042025-072026-10
Major 1Minor 1Patch 7

Each point covers 3 days.

OpenSSF Scorecard 5.8 / 10
5.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-10-19 04:28 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
10CI-Tests3 out of 3 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 8 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
PyPIclick>=8.1pyproject.toml
PyPIpandas>=2.1pyproject.toml
PyPIpyarrow>=14.0pyproject.toml
PyPIpyopenms>=3.3.0,<4.0.0pyproject.toml
PyPInumpy>=1.24pyproject.toml
PyPIduckdb>=1.3.0pyproject.toml
PyPIpyyaml>=6.0pyproject.toml
PyPIdefusedxml>=0.7.1pyproject.toml
PyPIsdrf-pipelines>=0.1.6pyproject.toml
PyPImudata>=0.3.1pyproject.toml
PyPIanndata>=0.9.0pyproject.toml
PyPIscipy>=1.10pyproject.toml
All dependencies 20

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

RegistryPackageVersionRelation
PyPIanndata—direct
PyPIclick—direct
PyPIdefusedxml—direct
PyPIduckdb—direct
PyPImudata—direct
PyPInumpy—direct
PyPIpandas—direct
PyPIpyarrow—direct
PyPIpyopenms—direct
PyPIpyyaml—direct
PyPIscipy—direct
PyPIsdrf-pipelines—direct
PyPIlxml—indirect
PyPImarkdown-exec—indirect
PyPImkdocs—indirect
PyPImkdocs-material—indirect
PyPImokume—indirect
PyPIplotly—indirect
PyPIpridepy—indirect
PyPIscikit-learn—indirect
Dependency advisories 0

Installing pypi:qpx@1.1.6 pulls in 41 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.