testing-library/svelte-testing-library
Grade a repo

78

/ 100

GradeC

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

Top 35% of 5,156 graded repos

:chipmunk: Simple and complete Svelte DOM testing utilities that encourage good testing practices

Documentation90
Engineering66
Health89
JavaScript661MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

16 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
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

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

90

Contributing guide5pt79

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

66

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.

Reproducibility6pt20

No dependency lockfile found (−70 pts).

→ Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.

CI/CD14pt57

CI is configured (.github/workflows/lint-pr.yml).

Tests18pt100

Test files detected (examples/basic/basic.test.js).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Project health

89

Dependency manifest6pt65

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

  • 6 / 11
    Commits (30d / 90d)
  • 32
    Forks
  • 86
    Releaseslatest 7y ago

Community

  • 62% - Fair
    Community health
  • 3 bus factor
    authors own >50% of commits
  • 661
    Watchers

Responsiveness

  • 2h
    Median issue response
  • 1h
    Median PR merge time
  • 1
    Open issues
Repository files25 root entries
  • .github
    Good: CI is configured (.github/workflows/lint-pr.yml).
    Good: Dependabot covers 2 ecosystems (npm, github-actions). Dependencies stay current.
  • examples
    Good: Test files detected (examples/basic/basic.test.js).
  • other
  • packages
  • scripts
  • tests
  • .all-contributorsrc
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • .prettierignore
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    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.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • eslint.config.js
  • jest.config.js
  • LICENSE
    Good: Licensed under MIT.
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-workspace.yaml
  • prettier.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.
    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.
  • release.config.js
  • svelte.config.js
  • tsconfig.json
  • vite.config.js
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/testing-library/svelte-testing-library)](https://www.repo-grade.com/report/testing-library/svelte-testing-library)

More graded JavaScript repos