Lots of room to improve. Start with a README and CI.
Documentation
34
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
CONTRIBUTING guide found.
A license file is present.
Engineering
52
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.
Test files detected (node_modules/gulp-autoprefixer/node_modules/gulp-util/node_modules/dateformat/node_modules/meow/node_modules/normalize-package-data/test).
CI is configured (node_modules/gulp-autoprefixer/node_modules/gulp-util/node_modules/dateformat/.travis.yml).
Linter or formatter configured (node_modules/gulp-autoprefixer/node_modules/autoprefixer/node_modules/caniuse-db/.editorconfig).
Project health
32
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
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).
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 files17 root entries
- .sass-cache
- bootstrap
- css
- img
- jquery-plugins
- js
- node_modulesGood: A license file is present.Good: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Test files detected (node_modules/gulp-autoprefixer/node_modules/gulp-util/node_modules/dateformat/node_modules/meow/node_modules/normalize-package-data/test).Good: CI is configured (node_modules/gulp-autoprefixer/node_modules/gulp-util/node_modules/dateformat/.travis.yml).Good: Linter or formatter configured (node_modules/gulp-autoprefixer/node_modules/autoprefixer/node_modules/caniuse-db/.editorconfig).Good: Security policy present.Issue: Build artifacts or local files may be committed (node_modules/.bin) (−40 pts).Fix: Remove them and add to .gitignore.
- scss
- about-us.html
- claims-payments.html
- contact-us.html
- gulpfile.js
- index.html
- orderform.php
- package.jsonGood: Dependency manifest found (package.json).
- products.html
- 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 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.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.