jetstreamapp/jetstream
Grade a repo

0

/ 100

GradeA

Polished and well engineered. Punching above its star count.

Top 7% of 5,156 graded repos

A better way to build on Salesforce

Documentation95
Engineering93
Health95
TypeScript121Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

11 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
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

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 guide5pt69

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 Other.

Engineering

93

Reproducibility6pt80

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

CI/CD14pt85

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

Tests18pt100

Test files detected (apps-sfdx/jest.config.js).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

95

Dependency manifest6pt85

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)
  • 30
    Forks
  • 416
    Releaseslatest 3y ago

Community

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

Responsiveness

  • 8d 13h
    Median issue response
  • <1h
    Median PR merge time
  • 187
    Open issues
Repository files60 root entries
  • .agents
  • .claude
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • .husky
  • .vscode
  • apps
  • apps-sfdx
    Good: Test files detected (apps-sfdx/jest.config.js).
  • build-resources
  • custom-express-typings
  • custom-typings
  • libs
  • mock-idp
  • playwright
  • prisma
  • scripts
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env.example
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mcp.json
  • .nvmrc
  • .nxignore
  • .prettierignore
  • .prettierrc
  • .release-it-desktop.json
  • .release-it-web-ext.json
  • .release-it.json
  • .svgo-config.json
  • AGENTS.md
  • babel.config.json
  • CHANGELOG.md
  • CLAUDE.md
  • commitlint.config.js
  • 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.
    Good: Contributing guide describes code style expectations.
    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.
  • DESKTOP_EULA.md
  • docker-compose.e2e.yml
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile.e2e
  • ecosystem.staging.config.js
  • electron-builder.config.js
  • eslint.config.js
  • jetstream-logo-white-plate.png
  • LICENSE.md
    Good: Licensed under Other.
  • migrations.json
  • next-sitemap.config.js
  • nx.json
  • package.json
    Good: Dependency manifest found (package.json).
  • playwright.config.base.ts
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • prisma.config.ts
  • proxy.conf.json
  • 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.
  • tsconfig.base.json
  • version.json
  • vitest.config.ts
  • vitest.workspace.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/jetstreamapp/jetstream)](https://www.repo-grade.com/report/jetstreamapp/jetstream)

More graded TypeScript repos