cin12211/orca-q
Grade a repo

0

/ 100

GradeB

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

Top 26% of 5,156 graded repos

The open source | Next Generation database editor

Documentation95
Engineering69
Health97
TypeScript204MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  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

95

Contributing guide5pt66

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.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

69

Tests18pt35

Test files detected (test).

Reproducibility6pt80

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

CI/CD14pt85

CI is configured (.github/workflows/api-tests.yml).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

97

Dependency manifest6pt90

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)
  • 13
    Forks
  • 10
    Releaseslatest 2mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 204
    Watchers

Responsiveness

  • -
    Median issue response
  • <1h
    Median PR merge time
  • 2
    Open issues
Repository files57 root entries
  • .agent
  • .agents
  • .claude
  • .codex
  • .github
    Good: CI is configured (.github/workflows/api-tests.yml).
    Good: Issue or PR templates present.
  • .husky
  • .opencode
  • .storybook
  • .tmp
  • .vscode
  • app
  • assets
  • build
  • components
  • core
  • docs
  • electron
  • layouts
  • lib
  • middleware
  • npx-package
  • pages
  • plugins
  • public
  • SAC
  • scripts
  • server
  • test
    Good: Test files detected (test).
  • types
  • .dependency-cruiser.js
  • .dockerignore
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • .mcp.json
  • .prettierignore
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • AGENTS.md
  • app.vue
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • components.json
  • 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.
    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).
    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.
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • ecosystem.config.js
  • electron-builder.yml
  • error.vue
  • LICENSE.txt
    Good: Licensed under MIT.
  • nuxt.config.ts
  • package.json
    Good: Dependency manifest found (package.json).
  • playwright.config.ts
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • tailwind.config.ts
  • tsconfig.json
  • vitest.config.ts
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/cin12211/orca-q)](https://www.repo-grade.com/report/cin12211/orca-q)

More graded TypeScript repos