pulsar-edit/package-backend
Grade a repo

89

/ 100

GradeB

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

Top 14% of 5,156 graded repos

Pulsar Registry Backend for Community Packages

Documentation73
Engineering99
Health89
JavaScript12MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

  2. 2
    Install and run instructions9pt

    Add a section showing how to start or use the project.

  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

73

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt64

Contributing guide is detailed and thorough.

README12pt85

README is present.

License6pt100

Licensed under MIT.

Engineering

99

Reproducibility6pt92

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

Tests18pt100

Test files detected (jest.config.js).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.js).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Dependency manifest6pt65

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

Community

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

Responsiveness

  • 14h
    Median issue response
  • 23h
    Median PR merge time
  • 32
    Open issues
Repository files32 root entries
  • .github
    Good: CI is configured (.github/workflows/ci-standards.yml).
    Good: Dependabot configured for npm.
    Good: Issue or PR templates present.
  • docs
  • scripts
  • src
  • tests
  • .all-contributorsrc
  • .codacy.yaml
  • .compactignore
  • .complexrc
  • .eslintrc.js
    Good: Linter or formatter configured (.eslintrc.js).
  • .gcloudignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .prettierignore
  • app.example.yaml
  • ARCHITECTURE.md
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codeql-config.yml
  • 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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • dispatch.yaml
  • FUNDING.yml
  • jest.config.js
    Good: Test files detected (jest.config.js).
  • jsdoc.conf.js
  • LICENSE.md
    Good: Licensed under MIT.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • PULL_REQUEST_TEMPLATE.md
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • SECURITY.md
    Good: Security policy present.
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/pulsar-edit/package-backend)](https://www.repo-grade.com/report/pulsar-edit/package-backend)

More graded JavaScript repos