apache/trafficserver

0

/ 100

Documentation85
Engineering66
Health100
C++1,959Apache-2.01d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

Apache Traffic Server™ is a fast, scalable and extensible HTTP/1.1 and HTTP/2 compliant caching proxy server.

Documentation

85

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt80

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

66

Reproducibility6pt22

No dependency lockfile found (−70 pts).

→ Commit poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.

CI/CD14pt40

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

Tests18pt80

Test files detected (example/plugins/c-api/protocol/test).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (setup.cfg).

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)
  • 864
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,959
    Watchers

Responsiveness

  • 16h
    Median issue response
  • 3h
    Median PR merge time
  • 435
    Open issues
Repository files47 root entries
  • .claude
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/cifuzz.yml).
  • .vscode
  • ci
    Good: Environment pinned via ci/docker/deb/Dockerfile.
  • cmake
  • configs
  • contrib
  • doc
  • example
    Good: Test files detected (example/plugins/c-api/protocol/test).
  • ext
  • include
  • lib
    Good: Code of conduct present.
    Good: Dependabot is configured. Dependencies update automatically.
    Good: Issue or PR templates present.
  • plugins
  • rc
  • src
  • tests
  • tools
  • .asf.yaml
  • .clang-analyzer
  • .clang-format
  • .clang-tidy
  • .cmake-format.yaml
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • .perltidyrc
  • .ripgreprc
  • .style.yapf
  • .tsan_suppressions
  • .vimrc
  • .yapfignore
  • AGENTS.md
  • CMakeLists.txt
  • CMakePresets.json
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
  • emacs-style
  • Findtsapi.cmake.in
  • INSTALL
  • LICENSE
    Good: Licensed under Apache-2.0.
  • NOTICE
  • README-EC2
    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.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • README.md
  • SECURITY.md
    Good: Security policy present.
  • setup.cfg
    Good: Dependency manifest found (setup.cfg).
  • STATUS
  • ts.pc.in