teviw000/dubuggerapp

0

/ 100

Documentation31
Engineering98
Health32
JavaScript05y ago
Grade a repo

Rough and inactive. Tests, CI, and a fuller README would revive it.

Documentation

31

README12pt0

No README found in the repository.

→ Add a README.md describing what the project does, how to install it, and how to run it.

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

Contributing guide5pt77

CONTRIBUTING guide found.

License6pt100

A license file is present.

Engineering

98

Reproducibility6pt80

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

Tests18pt100

Test files detected (node_modules/@bcoe/v8-coverage/src/test).

CI/CD14pt100

CI is configured (node_modules/@hapi/address/.travis.yml).

Linting and formatting5pt100

Linter or formatter configured (node_modules/@babel/highlight/node_modules/color-name/.eslintrc.json).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

32

Housekeeping3pt0

No .gitignore found (−60 pts).

→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Repository metadata5pt40

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 manifest6pt65

Dependency manifest found (package.json).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 0
    Watchers

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files5 root entries
  • node_modules
    Good: 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: Code of conduct present.
    Good: Test files detected (node_modules/@bcoe/v8-coverage/src/test).
    Good: CI is configured (node_modules/@hapi/address/.travis.yml).
    Good: Linter or formatter configured (node_modules/@babel/highlight/node_modules/color-name/.eslintrc.json).
    Good: Environment pinned via node_modules/@surma/rollup-plugin-off-main-thread/Dockerfile.
    Good: Issue or PR templates present.
    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.
  • public
  • src
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).