cboard-org/cboard
Grade a repo

0

/ 100

GradeB

Polished and well engineered. Punching above its star count.

Top 16% of 5,156 graded repos

Augmentative and Alternative Communication (AAC) system with text-to-speech for the browser

Documentation87
Engineering85
Health97
JavaScript738GPL-3.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

12 to address
  1. 1
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

87

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under GPL-3.0.

Engineering

85

CI/CD14pt57

CI is configured (.github/workflows/codeql-analysis.yml).

Reproducibility6pt80

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

Tests18pt100

Test files detected (src/__test__/helpers.test.js).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

97

Dependency manifest6pt90

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)
  • 273
    Forks
  • 75
    Releaseslatest 6y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 738
    Watchers

Responsiveness

  • 18d
    Median issue response
  • 9h
    Median PR merge time
  • 236
    Open issues
Repository files39 root entries
  • __mocks__
  • .agents
  • .circleci
  • .claude
  • .github
    Good: CI is configured (.github/workflows/codeql-analysis.yml).
    Good: Issue or PR templates present.
  • .vscode
  • docs
  • env
  • public
  • rootfs
  • scripts
  • src
    Good: Test files detected (src/__test__/helpers.test.js).
  • tests
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .eslintrc
  • .gitignore
    Good: .gitignore present.
  • .grenrc.json
  • .nvmrc
  • .prettierrc
  • browserstack.yml
  • CBOARD_SYMBOLS_INTEGRATION.md
  • cboard.njsproj.user
  • CHANGELOG.md
  • 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).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • craco.config.js
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • funding.json
  • LICENSE.txt
    Good: Licensed under GPL-3.0.
  • Makefile
  • package.json
    Good: Dependency manifest found (package.json).
  • playwright.config.ts
  • 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.
  • roadmap.md
  • skills-lock.json
  • sw-precache-config.js
  • tsconfig.json
  • yarn.lock
    Good: Lockfile present (yarn.lock). Installs are reproducible.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/cboard-org/cboard)](https://www.repo-grade.com/report/cboard-org/cboard)

More graded JavaScript repos