chromedevtools/devtools-frontend

0

/ 100

Documentation54
Engineering70
Health94
TypeScript3,944BSD-3-Clause1d ago
Grade a repo

Strong community interest, but tests, CI, or docs need work.

The Chrome DevTools UI

Documentation

54

Install and run instructions9pt10

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

→ Add a section showing how to install dependencies.

Contributing guide5pt52

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt65

README is present.

License6pt100

Licensed under BSD-3-Clause.

Engineering

70

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/CD14pt40

CI is configured (.github/workflows/auto-close-prs.yml).

Reproducibility6pt92

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

Tests18pt100

Test files detected (extensions/cxx_debugging/e2e/standalone/MemoryInspector.test.ts).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

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

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 3,944
    Watchers

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 123
    Open issues
Repository files52 root entries
  • .agents
  • .gemini
  • .github
    Good: CI is configured (.github/workflows/auto-close-prs.yml).
  • .vscode
  • build_overrides
  • config
  • docs
  • extension-api
  • extensions
    Good: Test files detected (extensions/cxx_debugging/e2e/standalone/MemoryInspector.test.ts).
  • front_end
    Good: Environment pinned via front_end/third_party/codemirror/package/mode/dockerfile.
  • inspector_overlay
  • mcp
  • node_modules
    Good: Code of conduct present.
    Good: Dependabot is configured. Dependencies update automatically.
    Issue: Build artifacts or local files may be committed (node_modules/.bin) (−40 pts).Fix: Remove them and add to .gitignore.
  • scripts
  • test
  • third_party
  • v8
  • .clang-format
  • .clang-format-ignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env.template
  • .geminiignore
  • .git-blame-ignore-revs
  • .gitallowed
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .gn
  • .mailmap
  • .npmignore
  • .npmrc
  • .style.yapf
  • .stylelintignore
  • .stylelintrc.json
  • AUTHORS
  • build
  • BUILD.gn
  • buildtools
  • codereview.settings
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • DEPS
  • DIR_METADATA
  • eslint.config.mjs
  • favicon.ico
  • LICENSE
    Good: Licensed under BSD-3-Clause.
  • OWNERS
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • PRESUBMIT.py
  • README.md
    Good: 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.
    Good: README includes status badges.
    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.
  • SECURITY.md
    Good: Security policy present.
  • WATCHLISTS