checkly/checkly-cli
Grade a repo

91

/ 100

GradeA

Well engineered for its size. A portfolio piece worth showing off.

Top 11% of 5,156 graded repos

TS/JS native Monitoring as Code workflow

Documentation86
Engineering99
Health79
TypeScript94Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

10 to address
  1. 1
    README12pt

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

  2. 2
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  3. 3
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  4. 4
    Reproducibility6pt

    Add additional package-ecosystem entries (especially github-actions) to keep all dependencies current.

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

86

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Contributing guide5pt100

Contributing guide is detailed and thorough.

Engineering

99

Reproducibility6pt92

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

Tests18pt100

Test files detected (benchmarks/large-playwright-project/tests).

CI/CD14pt100

CI is configured (.github/workflows/check-ai-context.yml).

Linting and formatting5pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

79

Dependency manifest6pt55

Dependency manifest found (package.json).

Housekeeping3pt60

.gitignore present.

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

  • 23 / 89
    Commits (30d / 90d)
  • 24
    Forks
  • 200
    Releaseslatest 5y ago

Community

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

Responsiveness

  • 1d 1h
    Median issue response
  • 15h
    Median PR merge time
  • 21
    Open issues
Repository files19 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/check-ai-context.yml).
    Good: Dependabot configured for npm.
    Good: Issue or PR templates present.
  • benchmarks
    Good: Test files detected (benchmarks/large-playwright-project/tests).
  • examples
  • packages
    Issue: Build artifacts or local files may be committed (packages/cli/src/services/__tests__/fixtures/playwright-json/node_modules/@playwright) (−40 pts).Fix: Remove them and add to .gitignore.
  • skills
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • AGENTS.md
  • CLAUDE.md
  • commitlint.config.js
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
  • eslint.config.mjs
    Good: Linter or formatter configured (eslint.config.mjs).
  • LICENSE
    Good: Licensed under Apache-2.0.
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • 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.
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/checkly/checkly-cli)](https://www.repo-grade.com/report/checkly/checkly-cli)

More graded TypeScript repos