85

/ 100

GradeB

Well engineered. The main gaps are CI and setup instructions.

Top 22% of 5,156 graded repos

💅 Beautiful and accessible drag and drop for lists with React. ⭐️ Star to support our work!

TypeScript3,989Other21d 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

76

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt80

Contributing guide is detailed and thorough.

README12pt85

README is present.

License6pt100

Licensed under Other.

Engineering

85

CI/CD14pt57

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

Reproducibility6pt80

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Tests18pt100

Test files detected (cypress/integration/content-security-policy.spec.ts).

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.js).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

98

Dependency manifest6pt93

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

  • 0 / 0
    Commits (30d / 90d)
  • 131
    Forks
  • 24
    Releaseslatest 4y ago

Community

  • 100% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 3,989
    Watchers

Responsiveness

  • 3d 1h
    Median issue response
  • 1h
    Median PR merge time
  • 142
    Open issues
Repository files42 root entries
  • .circleci
  • .github
    Good: CI is configured (.github/workflows/commitlint.yml).
    Good: Issue or PR templates present.
  • .husky
  • .storybook
  • csp-server
  • cypress
    Good: Test files detected (cypress/integration/content-security-policy.spec.ts).
  • docs
  • src
  • stories
  • test
  • test-reports
  • .browserslistrc
  • .commitlintrc.json
  • .czrc
  • .eslintignore
  • .eslintrc.js
    Good: Linter or formatter configured (.eslintrc.js).
  • .gitignore
    Good: .gitignore present.
  • .node-version
    Good: Environment pinned via .node-version.
  • .npmrc
  • .prettierignore
  • .prettierrc
  • .release-it.json
  • .stylelintignore
  • .stylelintrc.json
  • a11y-audit-parse.js
  • babel.config.js
  • browser-test-harness.js
  • 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.
    Good: Contributing guide explains how to run tests.
    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.
  • cypress.config.ts
  • jest.config.ts
  • LICENSE
    Good: Licensed under Other.
  • lighthouse.config.js
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • 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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • renovate.json5
  • rollup.config.mjs
  • SECURITY.md
    Good: Security policy present.
  • server-ports.js
  • tsconfig.json
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/hello-pangea/dnd)](https://www.repo-grade.com/report/hello-pangea/dnd)

More graded TypeScript repos