dipanita45/healconnect

0

/ 100

Documentation95
Engineering60
Health91
JavaScript43MIT3d ago
Grade a repo

Solid foundation. Invest in docs and CI to grow from here.

A health monitoring system that connects patients and doctors at one platform

Documentation

95

Contributing guide5pt71

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

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

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

60

Tests18pt35

Test files detected (.opencode/get-shit-done/bin/gsd-tools.test.js).

CI/CD14pt57

CI is configured (.github/workflows/auto-comment.yml).

Reproducibility6pt70

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

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.json).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

91

Dependency manifest6pt72

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files39 root entries
  • __tests__
  • .github
    Good: CI is configured (.github/workflows/auto-comment.yml).
    Good: Issue or PR templates present.
  • .opencode
    Good: Test files detected (.opencode/get-shit-done/bin/gsd-tools.test.js).
  • .vscode
  • components
  • context
  • data
  • docs
  • Downloads
    Good: Licensed under MIT.
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
    Good: Security policy present.
  • HealthConnect_Kit_Arduino_Code
  • hooks
  • lib
  • pages
  • public
  • scripts
  • styles
  • .env.example
  • .eslintrc.json
    Good: Linter or formatter configured (.eslintrc.json).
  • .gitignore
    Good: .gitignore present.
  • .stylelintrc.json
  • build_output_utf8.txt
  • build_output.txt
  • build_output2.txt
  • Code_of_Conduct.md
    Good: Code of conduct present.
  • contributing.md
  • cors.json
  • jest.config.js
  • jest.setup.js
  • jsconfig.json
  • License.md
  • middleware.js
  • next.config.js
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • postcss.config.js
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    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
  • tailwind.config.js
  • Untitled design (3).mp4