duckduckgo/apple-browsers
Grade a repo

82

/ 100

GradeB

Well engineered. The main gaps are the README and setup instructions.

Top 28% of 5,156 graded repos

DuckDuckGo iOS & macOS browsers

Documentation62
Engineering88
Health100
Swift240Apache-2.018d ago

Top fixes

Highest-impact changes first, ranked by point weight

15 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

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

62

Install and run instructions9pt45

README documents how to install the project.

README12pt55

README is present.

Contributing guide5pt61

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

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

License6pt100

Licensed under Apache-2.0.

Engineering

88

Tests18pt80

Test files detected (SharedPackages/AIChat/Tests).

CI/CD14pt85

CI is configured (.github/workflows/actionlint.yml).

Linting and formatting5pt100

Linter or formatter configured (.swiftlint.yml).

Reproducibility6pt100

Lockfile present (Gemfile.lock). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (Gemfile).

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

  • 453 / 1702
    Commits (30d / 90d)
  • 74
    Forks
  • 920
    Releaseslatest 1y ago

Community

  • 62% - Fair
    Community health
  • 8 bus factor
    authors own >50% of commits
  • 240
    Watchers

Responsiveness

  • 6d 7h
    Median issue response
  • 4h
    Median PR merge time
  • 132
    Open issues
Repository files27 root entries
  • .bundle
  • .claude
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/actionlint.yml).
    Good: Dependabot covers 2 ecosystems (gitsubmodule, swift). Dependencies stay current.
    Good: Issue or PR templates present.
  • .maestro
  • DuckDuckGo.xcworkspace
  • fastlane
  • iOS
  • macOS
  • scripts
  • SharedPackages
    Good: Test files detected (SharedPackages/AIChat/Tests).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .ruby-version
    Good: Environment pinned via .ruby-version.
  • .swiftlint.yml
    Good: Linter or formatter configured (.swiftlint.yml).
  • .xcode-version
  • AGENTS.md
  • CLAUDE.md
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • LICENSE.md
    Good: Licensed under Apache-2.0.
  • Mintfile
  • package-lock.json
  • package.json
  • 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.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
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/apple-browsers)](https://www.repo-grade.com/report/duckduckgo/apple-browsers)

More graded Swift repos