duckduckgo/content-scope-scripts
Grade a repo

79

/ 100

GradeC

Solid foundation. Invest in docs and CI to grow from here.

Top 33% of 5,156 graded repos

A collection of shared JavaScript and HTML projects that are used within our Browsers.

Documentation77
Engineering76
Health89
JavaScript70Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

10 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    README12pt

    Expand with a description, install steps, usage, and examples.

  3. 3
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  4. 4
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

77

README12pt45

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Contributing guide5pt100

Contributing guide is detailed and thorough.

Engineering

76

Tests18pt35

Test files detected (.github/scripts/anthropic-config.test.mjs).

CI/CD14pt100

CI is configured (.github/workflows/build-branch.yml).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Dependency manifest6pt65

Dependency manifest found (Package.swift).

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

  • 74 / 141
    Commits (30d / 90d)
  • 34
    Forks
  • 444
    Releaseslatest 4y ago

Community

  • 62% - Fair
    Community health
  • -
    authors own >50% of commits
  • 70
    Watchers

Responsiveness

  • 18h
    Median issue response
  • 1d 9h
    Median PR merge time
  • 135
    Open issues
Repository files38 root entries
  • .agents
  • .claude
  • .cursor
  • .github
    Good: Test files detected (.github/scripts/anthropic-config.test.mjs).
    Good: CI is configured (.github/workflows/build-branch.yml).
    Good: Dependabot covers 2 ecosystems (npm, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .playwright
  • build
  • guides
  • injected
  • messaging
  • scripts
  • Sources
  • special-pages
  • types-generator
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .netlifyignore
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .prettierignore
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • .stylelintrc.json
  • .swift-version
  • AGENTS.md
  • build-output.eslint.config.js
  • CLAUDE.md
  • CODEOWNERS
  • CODING_STYLE.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • eslint.config.js
  • LICENSE.md
    Good: Licensed under Apache-2.0.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
  • Package.swift
    Good: Dependency manifest found (Package.swift).
  • README.md
    Good: 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.
    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.
  • skills-lock.json
  • tsconfig.json
  • tsconfig.strict-core.json
  • typedoc.js
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/duckduckgo/content-scope-scripts)](https://www.repo-grade.com/report/duckduckgo/content-scope-scripts)

More graded JavaScript repos