Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 17:12 UTC

illumination-k / pubmed-client

RustMIT★ 1 star⑂ 0 forkssince Jun 2025View on GitHub ↗
KindLibraryCommand-line toolMCP serverNetwork serviceWeb interfacehow this is determined

illumination-k/pubmed-client holds a health index of 67 out of 100, placing it in the Good band. It scores highest on AI Readiness (89/100) and lowest on Community & Adoption (28/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

67
overall / 100
Good

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.

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

Ownership

Shogo KawamuraPersonal account
10 followers96 public repossince Sep 2018

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

Package ecosystems

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
16.6/36Commit cadence — 24/52 weeks with commits
18/18Commit volume — 195 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year195
human_commit_share0.84
days_since_last_push4
active_weeks_last_year24
How it's scored
27/27Ships releases — 5 releases published
36/36Release recency — latest release 11 days ago
19.8/27Release cadence — a release every ~47 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count5
latest_release_tagv0.4.0
releases_from_tagsno
days_since_latest_release11
mean_days_between_releases47
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?

28At Risk · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateno
How it's scored
33.7/80Monthly downloads — 336 downloads/month across crates, go
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespubmed-cli, pubmed-mcp, github.com/illumination-k/pubmed-client, pubmed-client, pubmed-parser, pubmed-formatter
dependents—
ecosystemscrates, go
total_downloads1,026
monthly_downloads336
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?

52Moderate · 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
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
29.1/42Issue resolution — 69% of issues closed
26.2/30PR acceptance — 216/247 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/14 approved changesets -- score normalized to 0
Inputs used
merged_prs216
open_issues16
closed_issues36
prs_merged_7d0
prs_decided_7d0
prs_merged_30d13
prs_decided_30d13
issue_closed_ratio0.692
closed_unmerged_prs31
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
7.5/25Owner reach — 10 followers of illumination-k
25/25Track record — 96 public repos, account ~7 yr old
Inputs used
followers10
owner_typeUser
is_verified—
owner_loginillumination-k
public_repos96
account_age_days2,908
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 6 package(s) on crates, go
35/35Publish recency — latest publish 11 days ago
20/20Version history — 6 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespubmed-cli, pubmed-mcp, github.com/illumination-k/pubmed-client, pubmed-client, pubmed-parser, pubmed-formatter
ecosystemscrates, go
any_deprecatedno
min_days_since_publish11

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows — 17 workflow(s)
24/24Tests present
16/16Linter config — Cargo.toml ([workspace.lints]), biome.json, clippy.toml, pubmed-cli/Cargo.toml ([lints]), pubmed-client-napi/Cargo.toml ([lints]), pubmed-client-py/Cargo.toml ([lints]), pubmed-client-py/pyproject.toml ([tool.ruff]), pubmed-client-wasm/Cargo.toml ([lints]), pubmed-client/Cargo.toml ([lints]), pubmed-formatter/Cargo.toml ([lints]), pubmed-mcp/Cargo.toml ([lints]), pubmed-parser/Cargo.toml ([lints]), ruff.toml
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 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

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://illumination-k.github.io/pubmed-client/
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://illumination-k.github.io/pubmed-client/
docs_sitehttps://illumination-k.github.io/pubmed-client/
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

50Moderate · 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 — 30 out of 30 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/14 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
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
7.5/7.5Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
4.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
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
2.2/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 84 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

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.

89Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 84 of 84 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes29,283
How it's scored
18/18One-command bootstrap — mise.toml, pubmed-client-py/docs/Makefile
22/22Automated tests
11/11Lint / format config — Cargo.toml ([workspace.lints]), biome.json, clippy.toml, pubmed-cli/Cargo.toml ([lints]), pubmed-client-napi/Cargo.toml ([lints]), pubmed-client-py/Cargo.toml ([lints]), pubmed-client-py/pyproject.toml ([tool.ruff]), pubmed-client-wasm/Cargo.toml ([lints]), pubmed-client/Cargo.toml ([lints]), pubmed-formatter/Cargo.toml ([lints]), pubmed-mcp/Cargo.toml ([lints]), pubmed-parser/Cargo.toml ([lints]), ruff.toml
11/11Static type checking — pubmed-client-napi/tsconfig.json, pubmed-client-py/py.typed, pubmed-client-wasm/tsconfig.json, website/tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 57 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 16 of the last 100 commits are automated dependency updates
9/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, pnpm-lock.yaml, uv.lock
has_dockerfileyes
typed_languageyes
bootstrap_filesmise.toml, pubmed-client-py/docs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configspubmed-client-napi/tsconfig.json, pubmed-client-py/py.typed, pubmed-client-wasm/tsconfig.json, website/tsconfig.json
agent_commit_share0.57
toolchain_manifestsCargo.toml, pubmed-cli/Cargo.toml, pubmed-client-go/go.mod, pubmed-client-go/rust/Cargo.toml, pubmed-client-napi/Cargo.toml, pubmed-client-py/Cargo.toml, pubmed-client-r/src/rust/Cargo.toml, pubmed-client-wasm/Cargo.toml, pubmed-client/Cargo.toml, pubmed-formatter/Cargo.toml, pubmed-mcp/Cargo.toml, pubmed-parser/Cargo.toml, pubmed-test-utils/Cargo.toml
dependency_bot_commit_share0.16
How it's scored
45/45Type-checkable code — Rust (statically typed)
55/55Manageable file sizes — 0/262 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes55,374
source_files_sampled262
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

1GitHub stars
1contributors
195commits, last 12 months
4days since last push
5releases
1bus factor
16open issues
crates.io, Go, npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'pubmed-client-py' from its registry
  • Could not fetch crates package 'pubmed-test-utils' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-10 17:12 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests30 out of 30 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/14 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
9Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
3Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities84 existing vulnerabilities detected
Direct dependencies 87
RegistryPackageVersion constraintManifest
crates.iopubmed-client—pubmed-cli/Cargo.toml
crates.ioclap4.0pubmed-cli/Cargo.toml
crates.iofutures-util0.3pubmed-cli/Cargo.toml
crates.iotokio1.0pubmed-cli/Cargo.toml
crates.ioserde—pubmed-cli/Cargo.toml
crates.ioserde_json—pubmed-cli/Cargo.toml
crates.ioanyhow—pubmed-cli/Cargo.toml
crates.iothiserror—pubmed-cli/Cargo.toml
crates.iotracing—pubmed-cli/Cargo.toml
crates.iotracing-subscriber0.3pubmed-cli/Cargo.toml
crates.ioindicatif0.18pubmed-cli/Cargo.toml
crates.iotracing-indicatif0.3pubmed-cli/Cargo.toml
crates.iotempfile3.8pubmed-cli/Cargo.toml
crates.ioaws-config1.5pubmed-cli/Cargo.toml
crates.ioaws-sdk-s31.60pubmed-cli/Cargo.toml
crates.ioasync-trait0.1pubmed-cli/Cargo.toml
crates.ionapi3pubmed-client-napi/Cargo.toml
crates.ionapi-derive3pubmed-client-napi/Cargo.toml
crates.iopubmed-client—pubmed-client-napi/Cargo.toml
crates.ioserde_json—pubmed-client-napi/Cargo.toml
crates.iotokio1pubmed-client-napi/Cargo.toml
crates.iopubmed-client—pubmed-client-py/Cargo.toml
crates.iopyo30.28.2pubmed-client-py/Cargo.toml
crates.iopyo3-stub-gen0.19pubmed-client-py/Cargo.toml
crates.iopyo3-stub-gen-derive0.19pubmed-client-py/Cargo.toml
crates.ioanyhow—pubmed-client-py/Cargo.toml
crates.ioserde—pubmed-client-py/Cargo.toml
crates.ioserde_json—pubmed-client-py/Cargo.toml
crates.iotokio1.0pubmed-client-py/Cargo.toml
crates.iopubmed-client—pubmed-client-wasm/Cargo.toml
crates.ioconsole_error_panic_hook0.1pubmed-client-wasm/Cargo.toml
crates.iojs-sys0.3pubmed-client-wasm/Cargo.toml
crates.ioserde-wasm-bindgen0.6pubmed-client-wasm/Cargo.toml
crates.iotsify0.5pubmed-client-wasm/Cargo.toml
crates.iowasm-bindgen0.2pubmed-client-wasm/Cargo.toml
crates.iowasm-bindgen-futures0.4pubmed-client-wasm/Cargo.toml
crates.ioweb-sys0.3pubmed-client-wasm/Cargo.toml
crates.iowee_alloc0.4pubmed-client-wasm/Cargo.toml
crates.iogetrandom0.4pubmed-client-wasm/Cargo.toml
crates.iouuid1.17pubmed-client-wasm/Cargo.toml
crates.ioanyhow—pubmed-client-wasm/Cargo.toml
crates.ioserde—pubmed-client-wasm/Cargo.toml
crates.ioserde_json—pubmed-client-wasm/Cargo.toml
crates.ioanyhow—pubmed-client/Cargo.toml
crates.ioasync-trait0.1pubmed-client/Cargo.toml
crates.iomoka0.12pubmed-client/Cargo.toml
crates.iopubmed-formatter—pubmed-client/Cargo.toml
crates.iopubmed-parser—pubmed-client/Cargo.toml
crates.ioquick-xml—pubmed-client/Cargo.toml
crates.iorand0.10pubmed-client/Cargo.toml
crates.ioredis1pubmed-client/Cargo.toml
crates.ioregex—pubmed-client/Cargo.toml
crates.iorusqlite0.40pubmed-client/Cargo.toml
crates.ioserde—pubmed-client/Cargo.toml
crates.ioserde_json—pubmed-client/Cargo.toml
crates.iothiserror—pubmed-client/Cargo.toml
crates.iotime0.3pubmed-client/Cargo.toml
crates.iotracing—pubmed-client/Cargo.toml
crates.iopubmed-parser—pubmed-formatter/Cargo.toml
crates.ioregex—pubmed-formatter/Cargo.toml
crates.ioserde—pubmed-formatter/Cargo.toml
crates.ioserde_json—pubmed-formatter/Cargo.toml
crates.ioserde_norway0.9pubmed-formatter/Cargo.toml
crates.iotracing—pubmed-formatter/Cargo.toml
crates.ioanyhow—pubmed-mcp/Cargo.toml
crates.iopubmed-client—pubmed-mcp/Cargo.toml
crates.ioserde—pubmed-mcp/Cargo.toml
crates.ioserde_json—pubmed-mcp/Cargo.toml
crates.iothiserror—pubmed-mcp/Cargo.toml
crates.iotracing—pubmed-mcp/Cargo.toml
crates.ioaxum0.8pubmed-mcp/Cargo.toml
crates.ioclap4pubmed-mcp/Cargo.toml
crates.iormcp3.1pubmed-mcp/Cargo.toml
crates.ioschemars1.0pubmed-mcp/Cargo.toml
crates.iotokio1.0pubmed-mcp/Cargo.toml
crates.iotracing-subscriber0.3pubmed-mcp/Cargo.toml
crates.ioquick-xml—pubmed-parser/Cargo.toml
crates.ioregex—pubmed-parser/Cargo.toml
crates.ioserde—pubmed-parser/Cargo.toml
crates.ioserde_json—pubmed-parser/Cargo.toml
crates.iothiserror—pubmed-parser/Cargo.toml
crates.iotracing—pubmed-parser/Cargo.toml
crates.iourlencoding—pubmed-parser/Cargo.toml
npm@docusaurus/core^3.10.2website/package.json
npm@docusaurus/preset-classic^3.10.2website/package.json
npmreact^19.2.7website/package.json
npmreact-dom^19.2.7website/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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 — crates.io, Go.