Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 20:27 UTC

klebgenomics / Kaptive

The tool for in silico serotyping

PythonGPL-3.0★ 65 stars⑂ 27 forkssince Jun 2016View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

klebgenomics/Kaptive holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (92/100) and lowest on AI Readiness (50/100). It was last updated 21 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

56 followers23 public repossince Mar 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIkaptive3.3.28201238 days agobioinformaticsgenomicsmicrobiologyserotyping

Metrics by category

Vitality

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

76Good · 21% of overall
How it's scored
28.8/36Push recency — last push 21 days ago
13.8/36Commit cadence — 20/52 weeks with commits
18/18Commit volume — 116 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year116
human_commit_share0.93
days_since_last_push21
active_weeks_last_year20
How it's scored
27/27Ships releases — 36 releases published
36/36Release recency — latest release 38 days ago
19.8/27Release cadence — a release every ~86.4 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count36
latest_release_tagv3.3.2
releases_from_tagsno
days_since_latest_release38
mean_days_between_releases86.4

Community & Adoption

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

60Moderate · 17% of overall
How it's scored
29.3/60Stars — 65 stars
11.8/25Forks — 27 forks
5/15Watchers — 9 watchers
Inputs used
forks27
stars65
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
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
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
38.9/80Monthly downloads — 820 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageskaptive
dependents—
ecosystemspypi
total_downloads—
monthly_downloads820
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?

70Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.5/22.5Commit distribution — top contributor authored 44% of commits
6.8/13.5Contributor breadth — 5 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled5
top_contributor_share0.443
How it's scored
40.8/42Issue resolution — 97% of issues closed
24.2/30PR acceptance — 25/31 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/28 approved changesets -- score normalized to 0
Inputs used
merged_prs25
open_issues1
closed_issues34
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.971
closed_unmerged_prs6
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
12.6/25Owner reach — 56 followers of klebgenomics
17/25Track record — 23 public repos, account ~3 yr old
Inputs used
followers56
owner_typeOrganization
is_verifiedno
owner_loginklebgenomics
public_repos23
account_age_days1,264

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

92Excellent · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 1 out of 1 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — http://klebgenomics.github.io/Kaptive/
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicsbioinformatics, microbial-genomics, serotyping
has_wikino
homepagehttp://klebgenomics.github.io/Kaptive/
docs_sitehttp://klebgenomics.github.io/Kaptive/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

52Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 1 out of 1 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
0/7.5Code-Review — Found 0/28 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 contributing companies or organizations
0/10Dangerous-Workflow — 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
7.5/7.5Maintained — 30 commit(s) and 1 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 — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4

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_packages5
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:kaptive@3.3.2 runtime dependency closure — what installing the published package pulls in — 5 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
21.2/40Legible commit history — 37 of 93 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.398
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — justfile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 7 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_filesjustfile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.07
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/45 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes42,576
source_files_sampled45
oversized_source_files0

Key facts

65GitHub stars
5contributors
116commits, last 12 months
21days since last push
36releases
2bus factor
1open 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 ★ / 27 ⇿
0Stars
27Forks
29Releases

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.

0510152025302722017-042021-102026-04
Major 1Minor 4Patch 15

Each point covers 9 days.

OpenSSF Scorecard 4.0 / 10
4.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-14 20:27 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/28 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 1 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
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
PyPInumpy>=2.4pyproject.toml
PyPInumba>=0.62pyproject.toml
PyPIrammappy>=0.1.3pyproject.toml
PyPIgb-io>=0.4pyproject.toml
All dependencies 46

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

RegistryPackageVersionRelation
PyPIgb-io0.4.0direct
PyPInumba0.65.1direct
PyPInumpy2.4.6direct
PyPIrammappy0.1.3direct
PyPIcertifi2026.7.22indirect
PyPIcharset-normalizer3.4.9indirect
PyPIclick8.4.1indirect
PyPIcolorama0.4.6indirect
PyPIdeepl1.30.0indirect
PyPIdeepmerge2.1.0indirect
PyPIghp-import2.1.0indirect
PyPIgriffelib2.1.0indirect
PyPIidna3.18indirect
PyPIjinja23.1.6indirect
PyPIjoblib1.5.3indirect
PyPIllvmlite0.47.0indirect
PyPImarkdown3.10.2indirect
PyPImarkupsafe3.0.3indirect
PyPImergedeep1.3.4indirect
PyPImkdocs1.6.1indirect
PyPImkdocs-autorefs1.4.4indirect
PyPImkdocs-get-deps0.2.2indirect
PyPImkdocstrings1.0.4indirect
PyPImkdocstrings-python2.0.5indirect
PyPInarwhals2.22.1indirect
PyPIorjson3.11.9indirect
PyPIpackaging26.2indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.10.0indirect
PyPIplotly6.8.0indirect
PyPIpyfgs0.0.2indirect
PyPIpygments2.20.0indirect
PyPIpymdown-extensions11.0.1indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpyyaml6.0.3indirect
PyPIpyyaml-env-tag1.1indirect
PyPIrequests2.34.2indirect
PyPIscikit-learn1.9.0indirect
PyPIscipy1.17.1indirect
PyPIscipy1.18.0indirect
PyPIsix1.17.0indirect
PyPIthreadpoolctl3.6.0indirect
PyPItomli2.4.1indirect
PyPIurllib32.7.0indirect
PyPIwatchdog6.0.0indirect
PyPIzensical0.0.46indirect
Dependency advisories 0

Installing pypi:kaptive@3.3.2 pulls in 5 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.