ory/sdk

0

/ 100

Documentation85
Engineering78
Health100
PHP179Apache-2.01d ago
Grade a repo

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

The place where Ory's SDKs are being auto-generated

Documentation

85

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt93

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

78

CI/CD14pt57

CI is configured (.github/workflows/docker-ci.yml).

Tests18pt80

Test files detected (clients/client/dart/test).

Reproducibility6pt80

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

Linting and formatting5pt100

Linter or formatter configured (clients/client/ruby/.rubocop.yml).

Issue and PR templates6pt100

Issue or PR templates present.

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

  • —
    Commits (30d / 90d)
  • 96
    Forks
  • 36
    Releaseslatest 4y ago

Community

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

Responsiveness

  • 20h
    Median issue response
  • 2h
    Median PR merge time
  • 58
    Open issues
Repository files22 root entries
  • .circleci
  • .github
    Good: CI is configured (.github/workflows/docker-ci.yml).
    Good: Issue or PR templates present.
  • .reports
  • clients
    Good: Test files detected (clients/client/dart/test).
    Good: Linter or formatter configured (clients/client/ruby/.rubocop.yml).
  • config
  • contrib
  • repos
  • scripts
  • spec
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .reference-ignore
  • 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.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • 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.
  • SECURITY.md
    Good: Security policy present.