wordplaydev/wordplay

0

/ 100

Documentation40
Engineering92
Health89
TypeScript87Other1d ago
Grade a repo

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

An accessible, language-inclusive, web-based educational programming language and IDE for creating interactive typography.

Documentation

40

Install and run instructions9pt10

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt30

README is present.

Contributing guide5pt47

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.

License6pt100

Licensed under Other.

Engineering

92

Reproducibility6pt70

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

CI/CD14pt85

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

Tests18pt100

Test files detected (scripts/updates.test.ts).

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.json).

Issue and PR templates6pt100

Issue or PR templates present.

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

  • —
    Commits (30d / 90d)
  • 104
    Forks
  • 18
    Releaseslatest 2y ago

Community

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

Responsiveness

  • 211d 2h
    Median issue response
  • <1h
    Median PR merge time
  • 147
    Open issues
Repository files38 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/unit.yml).
    Good: Issue or PR templates present.
  • .vscode
  • functions
  • migration_scripts
  • playwright
  • scripts
    Good: Test files detected (scripts/updates.test.ts).
  • src
  • static
  • tests
  • .env.demo-wordplay
  • .env.template
  • .eslintrc.json
    Good: Linter or formatter configured (.eslintrc.json).
  • .firebaserc
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .prettierignore
  • .prettierrc.json
  • ARCHITECTURE.md
  • CHANGELOG.md
  • CLAUDE.md
  • 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.
  • diff_output.txt
  • firebase.json
  • firestore.indexes.json
  • firestore.rules
  • LANGUAGE.md
  • LICENSE
    Good: Licensed under Other.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • playwright.config.ts
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • svelte.config.js
  • test-time.mjs
  • tsconfig.json
  • ui-debug.log
  • vite.config.js
  • vitest.config.ts