jetstreamapp/jetstream
Grade a repo

97

/ 100

GradeA

Excellent work. The main thing left to polish is a contributing guide.

Top 4% of 5,156 graded repos

A better way to build on Salesforce

Documentation95
Engineering99
Health95
TypeScript127Other24d ago

Outstanding. A score of 97/100 puts this repo in a very small tier of truly well-engineered projects.

Top fixes

Highest-impact changes first, ranked by point weight

8 to address
  1. 1
    Reproducibility6pt

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

  2. 2
    Dependency manifest6pt

    Add a `keywords` array to help people find your package on npm.

  3. 3
    Dependency manifest6pt

    Add a `homepage` field pointing to your docs or project website.

  4. 4
    Contributing guide5pt

    Show new contributors how to get a local dev environment running.

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 guide5pt67

Contributing guide is detailed and thorough.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

99

Reproducibility6pt92

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

Tests18pt100

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

CI/CD14pt100

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

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)
  • 29
    Forks
  • 512
    Releaseslatest 3y ago

Community

  • 87% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 127
    Watchers

Responsiveness

  • 14d 24h
    Median issue response
  • <1h
    Median PR merge time
  • 116
    Open issues
Repository files59 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot configured for github-actions.
    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
  • docs
  • libs
  • mock-idp
  • playwright
  • prisma
  • scripts
  • tools
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env.example
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mcp.json
  • .nvmrc
  • .nxignore
  • .oxfmtrc.json
  • .oxlintrc.json
  • .release-it-desktop.json
  • .release-it-web-ext.json
  • .release-it.json
  • .svgo-config.json
  • AGENTS.md
  • CLAUDE.md
  • commitlint.config.js
  • 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.
    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.
  • DESKTOP_EULA.html
  • docker-compose.e2e.yml
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile.e2e
  • ecosystem.staging.config.js
  • electron-builder.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
  • 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_REVIEW.md
  • SECURITY.md
    Good: Security policy present.
  • tsconfig.base.json
  • tsconfig.json
  • version.json
  • vitest.config.mts
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