ory/docs
Grade a repo

92

/ 100

GradeA

Polished and well engineered. Punching above its star count.

Top 10% of 5,156 graded repos

The Ory documentation

Documentation88
Engineering94
Health94
TypeScript163Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

9 to address
  1. 1
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  2. 2
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  3. 3
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  4. 4
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

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

88

README12pt70

README is present.

Contributing guide5pt93

Contributing guide is detailed and thorough.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

94

CI/CD14pt85

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

Reproducibility6pt85

Lockfile present (go.sum). Installs are reproducible.

Tests18pt100

Test files detected (code-examples/oathkeeper/ws/main_test.go).

Linting and formatting5pt100

Formatting enforced (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (go.mod).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 1,829
    Forks
  • 42
    Releaseslatest 7y ago

Community

  • 87% - Good
    Community health
  • -
    authors own >50% of commits
  • 163
    Watchers

Responsiveness

  • 27d 23h
    Median issue response
  • <1h
    Median PR merge time
  • 67
    Open issues
Repository files46 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Issue or PR templates present.
  • .reports
  • .vscode
  • code-examples
    Good: Test files detected (code-examples/oathkeeper/ws/main_test.go).
    Good: Environment pinned via code-examples/oathkeeper/docker-compose.yml.
    Issue: Build artifacts or local files may be committed (code-examples/protect-page-login/flutter_web_redirect/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • docs
  • logs
  • schemas
  • src
  • tests
  • .coderabbit.yaml
  • .editorconfig
    Good: Formatting enforced (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .prettierignore
  • .prettierrc.js
  • .reference-ignore
  • AGENTS.md
  • arrow-left.svg
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • docusaurus.config.ts
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • index.js
  • jest.config.js
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • package-lock.json
  • package.json
  • playwright.config.ts
  • 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.
  • SECURITY.md
    Good: Security policy present.
  • sidebars-agentic.ts
  • sidebars-b2b.ts
  • sidebars-ciam.ts
  • sidebars-integrates.ts
  • sidebars-network.ts
  • sidebars-oel.ts
  • sidebars-oss.ts
  • sidebars-quickstarts.ts
  • sidebars-workforce.ts
  • sidebars.ts
  • tailwind.config.js
  • tools.go
  • tsconfig.json
  • vercel.json
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/ory/docs)](https://www.repo-grade.com/report/ory/docs)

More graded TypeScript repos