pulsar-edit/pulsar
Grade a repo

60

/ 100

GradeD

Strong community interest, but tests, CI, or docs need work.

Higher than 44% of 5,156 graded repos

A Community-led Hyper-Hackable Text Editor

Documentation60
Engineering49
Health89
JavaScript4,080Other1mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (85).

See your top fixes
Now
D
60
Potential
B
85

Top fixes

Highest-impact changes first, ranked by point weight

18 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

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

60

README12pt40

README is present.

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt85

Contributing guide is detailed and thorough.

License6pt100

Licensed under Other.

Engineering

49

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Tests18pt35

Test files detected (integration/workspace.spec.js).

CI/CD14pt57

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

Reproducibility6pt80

Lockfile present (yarn.lock). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.js).

Project health

89

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt85

Dependency manifest found (package.json).

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

  • 6 / 76
    Commits (30d / 90d)
  • 187
    Forks
  • 41
    Releaseslatest 2y ago

Community

  • 87% - Good
    Community health
  • 5 bus factor
    authors own >50% of commits
  • 4,080
    Watchers

Responsiveness

  • 14d 13h
    Median issue response
  • 6d 23h
    Median PR merge time
  • 327
    Open issues
Repository files37 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
  • docs
  • dot-atom
  • exports
  • hooks
  • integration
    Good: Test files detected (integration/workspace.spec.js).
  • keymaps
  • locales
  • menus
  • packages
  • resources
  • script
  • spec
    Issue: Build artifacts or local files may be committed (spec/fixtures/packages/package-with-ignored-incompatible-native-module/node_modules/compatible-native-module) (−40 pts).Fix: Remove them and add to .gitignore.
  • src
  • static
  • vendor
  • .cirrus.yml
  • .codacy.yaml
  • .eslintignore
  • .eslintrc.js
    Good: Linter or formatter configured (.eslintrc.js).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .yarnrc
  • CHANGELOG.md
  • 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.
    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.
    Good: Contributing guide includes code examples.
  • LICENSE.md
    Good: Licensed under Other.
  • package.json
    Good: Dependency manifest found (package.json).
  • playwright.config.ts
  • pnpm-workspace.yaml
  • ppm
  • pulsar.sh
  • README.md
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    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.
    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.
    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.
    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.
  • yarn.lock
    Good: Lockfile present (yarn.lock). Installs are reproducible.
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/pulsar)](https://www.repo-grade.com/report/pulsar-edit/pulsar)

More graded JavaScript repos