wotakumoe/wotaku

0

/ 100

Documentation60
Engineering38
Health100
TypeScript2,873Othertoday
Grade a repo

Strong community interest, but tests, CI, or docs need work.

An otaku index for everything! ⭐ Star the project if you like it!

Documentation

60

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

README12pt75

README is present.

License6pt100

Licensed under Other.

Engineering

38

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

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.

Reproducibility6pt70

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

Tests18pt80

Test files detected (docs/public/glossary/audio/spec).

Project health

100

Dependency manifest6pt100

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

  • 250 / 855
    Commits (30d / 90d)
  • 133
    Forks
  • 0
    Releases

Community

  • 37% - Weak
    Community health
  • —
    authors own >50% of commits
  • 2,873
    Watchers

Responsiveness

  • 3h
    Median issue response
  • 1h
    Median PR merge time
  • 0
    Open issues
Repository files17 root entries
  • .github
  • .vscode
  • api
  • docs
    Good: Test files detected (docs/public/glossary/audio/spec).
  • .dprint.json
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .licenserc.json
  • LICENSE.md
    Good: Licensed under Other.
  • nitro.config.ts
  • 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.
    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.
    Good: README documents how to run the project.
  • svgo.config.mjs
  • tsconfig.json
  • unocss.config.ts
  • wrangler.toml