ryokun6/ryos
Grade a repo

0

/ 100

GradeB

Good community traction and solid fundamentals. Nearly in the top tier.

ryOS, made with Cursor

Documentation74
Engineering81
Health94
TypeScript1,177AGPL-3.0today

Documentation

74

Contributing guide5pt25

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

81

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.

Reproducibility6pt80

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

CI/CD14pt85

CI is configured (.github/workflows/build-and-deploy.yml).

Tests18pt100

Test files detected (tests).

Linting and formatting5pt100

Linter or formatter configured (eslint.config.js).

Project health

94

Dependency manifest6pt82

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)
  • 179
    Forks
  • 10
    Releaseslatest today

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,177
    Watchers

Responsiveness

  • -
    Median issue response
  • <1h
    Median PR merge time
  • 13
    Open issues
Repository files36 root entries
  • .cursor
    Good: .gitignore present.
  • .github
    Good: CI is configured (.github/workflows/build-and-deploy.yml).
  • api
  • build
  • docs
  • electron
  • public
  • scripts
  • src
  • tests
    Good: Test files detected (tests).
  • .dockerignore
  • .gitignore
  • .hintrc
  • .mise.toml
  • .vercelignore
  • .version
  • AGENTS.md
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • bun.lockb
  • bunfig.toml
  • components.json
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • electron-builder.yml
  • eslint.config.js
    Good: Linter or formatter configured (eslint.config.js).
  • index.html
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • middleware.ts
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    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.
  • tailwind.config.js
  • tsconfig.app.json
  • tsconfig.json
  • tsconfig.node.json
  • vercel.json
  • vite.config.ts