jashkenas/underscore
Grade a repo

68

/ 100

GradeD

A workable base with real gaps. Start with setup instructions and the README.

Top 48% of 5,156 graded repos

JavaScript's utility _ belt

Documentation46
Engineering72
Health95
JavaScript27,333MIT2mo 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 A (90).

See your top fixes
Now
D
68
Potential
A
90

Top fixes

Highest-impact changes first, ranked by point weight

19 to address
  1. 1
    CI/CD14pt

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

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

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

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

46

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt40

README is present.

Contributing guide5pt78

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.

License6pt100

Licensed under MIT.

Engineering

72

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.

CI/CD14pt57

CI is configured (.github/workflows/codeql-analysis.yml).

Reproducibility6pt70

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

Tests18pt100

Test files detected (test).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Project health

95

Activity5pt80

Actively maintained (pushed within 3 months).

Dependency manifest6pt100

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 5,442
    Forks
  • 0
    Releases

Community

  • 85% - Good
    Community health
  • 3 bus factor
    authors own >50% of commits
  • 27,333
    Watchers

Responsiveness

  • 2h
    Median issue response
  • 12h
    Median PR merge time
  • 56
    Open issues
Repository files43 root entries
  • .github
    Good: CI is configured (.github/workflows/codeql-analysis.yml).
  • docs
  • modules
  • patches
  • test
    Good: Test files detected (test).
  • test-treeshake
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .eslintrc
  • .gitignore
    Good: .gitignore present.
  • .travis.yml
  • bower.json
  • CNAME
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
    Good: Contributing guide includes setup/install instructions.
    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.
  • favicon.ico
  • index.html
  • karma.conf-sauce.js
  • karma.conf.js
  • LICENSE
    Good: Licensed under MIT.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • 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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • rollup.common.js
  • rollup.config.js
  • rollup.config2.js
  • SECURITY.md
    Good: Security policy present.
  • underscore-esm-min.js
  • underscore-esm-min.js.map
  • underscore-esm.js
  • underscore-esm.js.map
  • underscore-min.js
  • underscore-min.js.map
  • underscore-node-f.cjs
  • underscore-node-f.cjs.map
  • underscore-node.cjs
  • underscore-node.cjs.map
  • underscore-node.mjs
  • underscore-node.mjs.map
  • underscore-umd-min.js
  • underscore-umd-min.js.map
  • underscore-umd.js
  • underscore-umd.js.map
  • underscore.js
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/jashkenas/underscore)](https://www.repo-grade.com/report/jashkenas/underscore)

More graded JavaScript repos