medic/cht-core

0

/ 100

Documentation84
Engineering92
Health92
JavaScript550AGPL-3.01d ago
Grade a repo

Polished and well engineered. Punching above its star count.

The CHT Core Framework makes it faster to build responsive, offline-first digital health apps that equip health workers to provide better care in their communities. It is a central resource of the Community Health Toolkit.

Documentation

84

Contributing guide5pt52

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

92

CI/CD14pt72

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

Tests18pt100

Test files detected (.mocharc.js).

Linting and formatting5pt100

Linter or formatter configured (config/covid-19/.eslintrc).

Reproducibility6pt100

Lockfile present (package-lock.json). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

92

Dependency manifest6pt75

Dependency manifest found (package.json).

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)
  • 401
    Forks
  • 145
    Releaseslatest 10y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 550
    Watchers

Responsiveness

  • 2d 3h
    Median issue response
  • 11h
    Median PR merge time
  • 721
    Open issues
Repository files40 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Dependabot covers 4 ecosystems (npm, npm, github-actions, npm). Dependencies stay current.
    Good: Issue or PR templates present.
  • .husky
  • admin
  • api
    Good: Environment pinned via api/Dockerfile.
  • config
    Good: Linter or formatter configured (config/covid-19/.eslintrc).
  • couchdb
  • couchdb-nouveau
  • ddocs
  • haproxy
  • haproxy-healthcheck
  • nginx
  • patches
  • release-notes
  • scripts
  • sentinel
  • shared-libs
  • tests
  • webapp
  • .browserslistrc
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .mocharc.js
    Good: Test files detected (.mocharc.js).
  • .sonarcloud.properties
  • AGENTS.md
  • Changes.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • commitlint.config.js
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • DEVELOPMENT.md
  • eslint.config.js
  • funding.json
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • TESTING.md