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

Clinical-Genomics / preClinVar

A ClinVar API submission helper written in FastAPI

PythonMIT★ 1 star⑂ 0 forkssince Jun 2022View on GitHub ↗
KindNetwork servicehow this is determined

Clinical-Genomics/preClinVar holds a health index of 35 out of 100, placing it in the Weak band. It scores highest on Engineering Quality (52/100) and lowest on AI Readiness (29/100). It was last updated 186 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Clinical GenomicsOrganization
96 followers123 public repossince Jan 2014

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

Metrics by category

Vitality

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

38Weak · 21% of overall
How it's scored
3.6/36Push recency — last push 186 days ago
1.4/36Commit cadence — 2/52 weeks with commits
11.9/18Commit volume — 20 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year20
human_commit_share1
days_since_last_push186
active_weeks_last_year2
How it's scored
27/27Ships releases — 19 releases published
16.2/36Release recency — latest release 186 days ago
19.8/27Release cadence — a release every ~83.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count19
latest_release_tagv2.9
releases_from_tagsno
days_since_latest_release186
mean_days_between_releases83.9
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?

36Weak · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars1
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes

Sustainability & Governance

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

51Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
36.5/42Issue resolution — 87% of issues closed
27.8/30PR acceptance — 88/95 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 1/8 approved changesets -- score normalized to 1
Inputs used
merged_prs88
open_issues9
closed_issues60
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.87
closed_unmerged_prs7
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
30/30Ownership backing — organization-owned
0/20Verified domain
14.3/25Owner reach — 96 followers of Clinical-Genomics
25/25Track record — 123 public repos, account ~12 yr old
Inputs used
followers96
owner_typeOrganization
is_verifiedno
owner_loginClinical-Genomics
public_repos123
account_age_days4,623

Engineering Quality

Are baseline engineering and documentation practices in place?

52Moderate · 19% of overall
How it's scored
24/24CI workflows — 8 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests — 3 out of 8 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

47Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0.8/2.5CI-Tests — 3 out of 8 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 1/8 approved changesets -- score normalized to 1
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
2/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_aggregate5
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.
How it's scored
6.2/35Direct dependencies free of known advisories — 5 affected: python-multipart 0.0.20 (high 8.6), setuptools 71.1.0 (high 8.8), urllib3 2.2.3 (high 7.5), +2 more
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
21.1/40No advisories left outstanding — 5 advisory-carrying package(s) unaddressed past 90 days; oldest published 483 days ago
Inputs used
sourceosv
advisories51
affected_packages8
assessed_packages41
unassessed_packages0
affected_by_severityhigh 5, moderate 3
direct_affected_packages5
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 41 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

29At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
12.8/40Legible commit history — 24 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.24
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
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
lockfilespoetry.lock
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/13 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes16,789
source_files_sampled13
oversized_source_files0

Key facts

1GitHub stars
1contributors
20commits, last 12 months
186days since last push
19releases
1bus factor
9open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch pypi package 'preClinVar' from its registry

More detail

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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 14:12 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
3CI-Tests3 out of 8 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 1/8 approved changesets -- score normalized to 1
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 16
RegistryPackageVersion constraintManifest
PyPIfastapi^0.115.2pyproject.toml
PyPIuvicorn^0.18.2pyproject.toml
PyPIgunicorn^23.0.0pyproject.toml
PyPIisort^5.10.1pyproject.toml
PyPIpython-multipart0.0.20pyproject.toml
PyPIjsonschema^4.21.1pyproject.toml
PyPIresponses^0.21.0pyproject.toml
PyPIhttpx^0.27.0pyproject.toml
PyPIsetuptools^71.0.1pyproject.toml
PyPIimportlib-resources^6.4.0pyproject.toml
PyPIzipp^3.20.2pyproject.toml
PyPIurllib3^2.2.3pyproject.toml
PyPIrequests^2.32.3pyproject.toml
PyPIidna^3.10pyproject.toml
PyPIplatformdirs^4.3.6pyproject.toml
PyPIcertifi2024.07.04pyproject.toml
All dependencies 41

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

RegistryPackageVersionRelation
PyPIcertifi2024.7.4direct
PyPIfastapi0.115.14direct
PyPIgunicorn23.0.0direct
PyPIhttpx0.27.2direct
PyPIidna3.11direct
PyPIimportlib-resources6.4.5direct
PyPIisort5.13.2direct
PyPIjsonschema4.23.0direct
PyPIplatformdirs4.3.6direct
PyPIpython-multipart0.0.20direct
PyPIrequests2.32.4direct
PyPIresponses0.21.0direct
PyPIsetuptools71.1.0direct
PyPIurllib32.2.3direct
PyPIuvicorn0.18.3direct
PyPIzipp3.20.2direct
PyPIannotated-types0.7.0indirect
PyPIanyio4.5.2indirect
PyPIattrs25.3.0indirect
PyPIcharset-normalizer3.4.5indirect
PyPIclick8.1.8indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.6.1indirect
PyPIexceptiongroup1.3.1indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIiniconfig2.1.0indirect
PyPIjsonschema-specifications2023.12.1indirect
PyPIpackaging26.0indirect
PyPIpkgutil-resolve-name1.3.10indirect
PyPIpluggy1.5.0indirect
PyPIpydantic2.10.6indirect
PyPIpydantic-core2.27.2indirect
PyPIpytest7.4.4indirect
PyPIpytest-cov3.0.0indirect
PyPIreferencing0.35.1indirect
PyPIrpds-py0.20.1indirect
PyPIsniffio1.3.1indirect
PyPIstarlette0.44.0indirect
PyPItomli2.4.0indirect
PyPItyping-extensions4.13.2indirect
Dependency advisories 8

This repository publishes no package the index resolves, so its own dependency graph was assessed — 41 packages, which also include development and test pins that never ship: 8 carry known advisories, of which 5 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
python-multipart0.0.20directhigh140.0.31
setuptools71.1.0directhigh483.0.0
urllib32.2.3directhigh122.7.0
click8.1.8indirecthigh18.3.3
starlette0.44.0indirecthigh141.3.1
idna3.11directmoderate23.15
requests2.32.4directmoderate22.33.0
pytest7.4.4indirectmoderate29.0.3

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.