0
/ 100
Strong community interest, but tests, CI, or docs need work.
:arrow_left: String left pad -- deprecated, use String.prototype.padStart()
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 C (72).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2README12pt
Expand with a description, install steps, usage, and examples.
- 3README12pt
Add more sections (Overview, Install, Usage, Contributing) using ## headings.
- 4README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
64
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
58
No linter or formatter found.
→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.
No dependency lockfile found (−70 pts).
→ Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.
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.
A test script is configured in package.json.
CI is configured (.travis.yml).
Project health
70
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
Dependency manifest found (package.json).
Repository has a description.
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 137Forks
- 0Releases
Community
- 37% - WeakCommunity health
- 2 bus factorauthors own >50% of commits
- 1,303Watchers
Responsiveness
- 10hMedian issue response
- 11hMedian PR merge time
- 10Open issues
Repository files9 root entries
- perf
- .gitignoreGood: .gitignore present.
- .travis.ymlGood: CI is configured (.travis.yml).
- index.d.ts
- index.js
- LICENSEGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## 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.Good: README has code examples.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.Good: README documents how to run the project.
- test.js
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/azer/left-pad)