Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 03:22 UTC

gwastro / pycbc

Core package to analyze gravitational-wave data, find signals, and study their parameters. This package was used in the first direct detection of gravitational waves (GW150914), and is used in the ongoing analysis of LIGO/Virgo data.

PythonGPL-3.0★ 391 stars⑂ 389 forkssince Mar 2015View on GitHub ↗

gwastro/pycbc holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Vitality (91/100) and lowest on Security (21/100). It was last updated today. 3 contributors account for most of its recent work.

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

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

Ownership

Gravitational-wave AstronomyOrganization · verified domain
126 followers70 public repossince Mar 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIPyCBC2.11.024,497154186 days agoligophysicsgravitysignal-processinggravitational-waves

Metrics by category

Vitality

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

91Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
28.4/36Commit cadence — 41/52 weeks with commits
18/18Commit volume — 169 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year169
human_commit_share1
days_since_last_push0
active_weeks_last_year41
How it's scored
27/27Ships releases — 100 releases published
27/36Release recency — latest release 118 days ago
27/27Release cadence — a release every ~30.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv2.8.7
releases_from_tagsno
days_since_latest_release118
mean_days_between_releases30.3

Community & Adoption

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

79Good · 17% of overall
How it's scored
42/60Stars — 391 stars
21.6/25Forks — 389 forks
8.7/15Watchers — 37 watchers
Inputs used
forks389
stars391
watchers37
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, shields.io, travis-ci.org
has_pull_request_templateyes
How it's scored
58.5/80Monthly downloads — 24,497 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesPyCBC
dependents—
ecosystemspypi
total_downloads—
monthly_downloads24,497
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?

82Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
14.6/22.5Commit distribution — top contributor authored 35% of commits
13.5/13.5Contributor breadth — 100 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor3
contributors_sampled100
top_contributor_share0.351
How it's scored
34/42Issue resolution — 81% of issues closed
26.9/30PR acceptance — 4,014/4,474 decided PRs merged
8.7/13Newcomer PR acceptance — 4/6 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs4,014
open_issues176
closed_issues744
prs_merged_7d12
prs_decided_7d14
prs_merged_30d34
prs_decided_30d48
issue_closed_ratio0.809
closed_unmerged_prs460
first_time_authors_30d4
first_time_prs_merged_30d4
first_time_prs_decided_30d6
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
15.1/25Owner reach — 126 followers of gwastro
25/25Track record — 70 public repos, account ~11 yr old
Inputs used
followers126
owner_typeOrganization
is_verifiedyes
owner_logingwastro
public_repos70
account_age_days4,249
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
26/35Publish recency — latest publish 186 days ago
20/20Version history — 154 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesPyCBC
ecosystemspypi
any_deprecatedno
min_days_since_publish186

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows — 14 workflow(s)
24/24Tests present
16/16Linter config — .pylintrc, ruff.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — http://pycbc.org
10/10Repository description
10/10Topics — 17 topics
10/10Wiki
Inputs used
topicsastronomy, physics, gravity, ligo, gravitational-waves, pycbc, analysis, python, black-hole, neutron-star, gwastro, virgo, signal-processing, open-science, cosmic-explorer, einstein-telescope, lisa
has_wikiyes
homepagehttp://pycbc.org
docs_sitehttp://pycbc.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

21At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestspyproject.toml, requirements-igwn.txt, requirements.txt, setup.py
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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_packages47
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:PyCBC@2.11.0 runtime dependency closure — what installing the published package pulls in — 47 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
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 99 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.99
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes4,997
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .pylintrc, ruff.toml
0/11Static type checking
10/10Reproducible environment — Dockerfile
10/10Demonstrated agent practice — 16 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.16
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
53.1/55Manageable file sizes — 15/439 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes109,911
source_files_sampled439
oversized_source_files15
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, notebooks
Inputs used
example_dirsexamples, notebooks
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

391GitHub stars
100contributors
169commits, last 12 months
0days since last push
100releases
3bus factor
176open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • First-time contributor figures cover 12 of 14 authors (cap 12)
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Star and fork history 0 ★ / 389 ⇿
0Stars
389Forks
100Releases

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.

012525037537562015-032020-122026-09
Major 1Minor 17Patch 82

Each point covers 11 days.

All dependencies 45

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

RegistryPackageVersionRelation
PyPIamqplib—indirect
PyPIastropy—indirect
PyPIbeautifulsoup4—indirect
PyPIboto3—indirect
PyPIcertifi—indirect
PyPIciecplib—indirect
PyPIcython—indirect
PyPIdqsegdb2—indirect
PyPIdynesty—indirect
PyPIemcee—indirect
PyPIgitpython—indirect
PyPIgwdatafind—indirect
PyPIh5py—indirect
PyPIhtchirp—indirect
PyPIigwn-ligolw—indirect
PyPIigwn-segments—indirect
PyPIjinja2—indirect
PyPIlalsuite—indirect
PyPIligo-gracedb—indirect
PyPIligo-proxy-utils—indirect
PyPIlscsoft-glue—indirect
PyPImako—indirect
PyPImarkupsafe—indirect
PyPImatplotlib—indirect
PyPImpld3—indirect
PyPInumpy—indirect
PyPIpegasus-wms—indirect
PyPIpegasus-wms-api—indirect
PyPIpegasus-wms-common—indirect
PyPIpegasus-wms-worker—indirect
PyPIpillow—indirect
PyPIpycuda—indirect
PyPIpyjwt—indirect
PyPIpykerr—indirect
PyPIpyyaml—indirect
PyPIs3transfer—indirect
PyPIscikit-cuda—indirect
PyPIscipy—indirect
PyPIsetuptools—indirect
PyPIsphinx—indirect
PyPIsphinx-design—indirect
PyPIsphinx-rtd-theme—indirect
PyPIsphinxcontrib-programoutput—indirect
PyPItqdm—indirect
PyPIurllib3—indirect
Dependency advisories 0

Installing pypi:PyCBC@2.11.0 pulls in 47 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.