userver-framework/userver
Grade a repo

0

/ 100

GradeA

A well-known project done right. Strong docs and solid engineering throughout.

Production-ready C++ Asynchronous Framework with rich functionality

Documentation88
Engineering87
Health100
C++2,909Apache-2.0today

Documentation

88

Contributing guide5pt58

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.

Install and run instructions9pt90

README documents how to install the project.

README12pt93

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

87

Tests18pt80

Test files detected (chaotic-openapi/golden_tests/output/client/include/clients/test).

CI/CD14pt85

CI is configured (.github/workflows/ci-conan.yml).

Reproducibility6pt92

Lockfile present (samples/dns-resolver/requirements.txt). Installs are reproducible.

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 (pyproject.toml).

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)
  • 396
    Forks
  • 19
    Releaseslatest 1y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 2,909
    Watchers

Responsiveness

  • 16h
    Median issue response
  • 9h
    Median PR merge time
  • 147
    Open issues
Repository files49 root entries
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/ci-conan.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • chaotic
  • chaotic-openapi
    Good: Test files detected (chaotic-openapi/golden_tests/output/client/include/clients/test).
  • clickhouse
  • cmake
  • core
  • grpc
  • kafka
  • libraries
  • mongo
  • mysql
  • odbc
  • otlp
  • postgresql
  • rabbitmq
  • redis
  • rocks
  • samples
    Good: Lockfile present (samples/dns-resolver/requirements.txt). Installs are reproducible.
  • scripts
  • scylla
  • service_template
  • sqlite
  • testsuite
  • third_party
  • universal
  • ydb
  • .clang-format
  • .clang-tidy
  • .cmake-format.py
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mapping.json
  • .piglet-meta.json
  • AUTHORS
  • CMakeLists.txt
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CODEOWNERS
  • conanfile.py
  • 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).
    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.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • pytest.ini
  • README.md
    Good: README is present.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • THIRD_PARTY.md
  • version.txt