contour-terminal/contour
Grade a repo

0

/ 100

GradeB

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

Modern C++ Terminal Emulator

Documentation95
Engineering78
Health100
C++2,947Apache-2.0today

Documentation

95

Contributing guide5pt83

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.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

78

CI/CD14pt57

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

Tests18pt80

Test files detected (test).

Reproducibility6pt80

Lockfile present (docs/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 (docs/requirements.txt).

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)
  • 142
    Forks
  • 38
    Releaseslatest 4y ago

Community

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

Responsiveness

  • 39d 14h
    Median issue response
  • 8h
    Median PR merge time
  • 196
    Open issues
Repository files25 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Environment pinned via .github/appimage/Dockerfile.
    Good: Issue or PR templates present.
  • cmake
  • docs
    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.
    Good: Contributing guide includes setup/install instructions.
    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.
    Good: Contributing guide includes code examples.
    Good: Lockfile present (docs/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (docs/requirements.txt).
  • examples
  • scripts
  • src
  • test
    Good: Test files detected (test).
  • .clang-format
  • .codecov.yml
  • .ecrc
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .spellcheck.yml
  • autogen.sh
  • CMakeLists.txt
  • CMakePresets.json
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • cspell.json
  • LICENSE.txt
    Good: Licensed under Apache-2.0.
  • metainfo.xml
  • mkdocs.yml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
  • vcpkg-configuration.json
  • vcpkg.json