Good shape overall. A few tweaks would push it into the top tier.

BioMCP: Biomedical Model Context Protocol

Documentation

81

Contributing guide5pt69

Contributing guide is detailed and thorough.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

67

Linting and formatting5pt0

No linter or formatter config found.

Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Reproducibility6pt70

Lockfile present (Cargo.lock). Installs are reproducible.

Tests18pt80

Test files detected (architecture/experiments/243-architecture-hpo-phenotype-enrichment-for-clinical-symptoms/scripts/test_clinical_features_spike.py).

CI/CD14pt100

CI is configured (.github/workflows/ci.yml).

Project health

100

Dependency manifest6pt100

Dependency manifest found (Cargo.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 107
    Forks
  • 60
    Releaseslatest 1y ago

Community

  • Community health
  • authors own >50% of commits
  • 529
    Watchers

Responsiveness

  • 9h
    Median issue response
  • 2h
    Median PR merge time
  • 0
    Open issues
Repository files47 root entries
  • .claude-plugin
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • .march
  • architecture
    Good: Test files detected (architecture/experiments/243-architecture-hpo-phenotype-enrichment-for-clinical-symptoms/scripts/test_clinical_features_spike.py).
  • benchmarks
  • bin
  • coverage
  • crates
  • docs
  • examples
  • paper
  • protos
  • scripts
  • skills
  • spec
  • src
  • templates
  • testdata
  • tests
  • tools
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mcpbignore
  • .rustfmt.toml
  • .zenodo.json
  • AGENTS.md
  • build.rs
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • CHECKLIST.md
  • CITATION.cff
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • DEAD-CODE-EVALUATION.md
  • deny.toml
  • install.sh
  • LICENSE
    Good: Licensed under MIT.
  • Makefile
  • manifest.json
  • mkdocs.yml
  • PATTERN.md
  • pyproject.toml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • RUN.md
  • TEST-REBUILD.md
  • uv.lock