Solid engineering. The main gap is visibility.
Documentation
69
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
96
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (01_helloWorld/helloWorld.spec.js).
CI is configured (.circleci/config.yml).
Linter or formatter configured (.eslintrc.json).
Issue or PR templates present.
Project health
57
No pushes in over a year (−80 pts).
→ A recent commit signals the project is alive and worth contributing to.
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (package.json).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 0Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files25 root entries
- .circleciGood: CI is configured (.circleci/config.yml).
- .githubGood: Issue or PR templates present.
- 01_helloWorldGood: Test files detected (01_helloWorld/helloWorld.spec.js).
- 02_repeatString
- 03_reverseString
- 04_removeFromArray
- 05_sumAll
- 06_leapYears
- 07_tempConversion
- 08_calculator
- 09_palindromes
- 10_fibonacci
- 11_getTheTitles
- 12_findTheOldest
- archive
- generators
- .eslintignore
- .eslintrc.jsonGood: Linter or formatter configured (.eslintrc.json).
- .gitignoreGood: .gitignore present.
- .npmrc
- LICENSEGood: Licensed under MIT.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- plopFile.js
- README.mdGood: README is present.Good: README is well structured with multiple sections.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.Good: README documents how to run the project.