williamkapke/kapture

0

/ 100

Documentation59
Engineering54
Health100
JavaScript1631d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

Chrome DevTools Extension that enables browser automation through MCP

Documentation

59

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt0

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

Engineering

54

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

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/build-extension.yml).

Reproducibility6pt70

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

Tests18pt80

Test files detected (e2e/.mocharc.json).

Project health

100

Dependency manifest6pt100

Dependency manifest found (e2e/package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 46
    Forks
  • 10
    Releaseslatest 11mo ago

Community

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

Responsiveness

  • 11d 4h
    Median issue response
  • 3h
    Median PR merge time
  • 5
    Open issues
Repository files12 root entries
  • .github
    Good: CI is configured (.github/workflows/build-extension.yml).
  • e2e
    Good: Test files detected (e2e/.mocharc.json).
    Good: Lockfile present (e2e/package-lock.json). Installs are reproducible.
    Good: Dependency manifest found (e2e/package.json).
  • extension
  • server
  • specs
  • test-app
  • website
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • INITIAL_PRODUCT_SPEC.md
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
  • scratch.mjs