gui-cs/terminal.gui
Grade a repo

89

/ 100

GradeB

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

Top 14% of 5,156 graded repos

Cross Platform Terminal UI toolkit for .NET

Documentation96
Engineering80
Health100
C#11,084MIT2mo ago

Top fixes

Highest-impact changes first, ranked by point weight

7 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

96

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt93

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

80

Reproducibility6pt30

No dependency lockfile found (−70 pts).

→ Enable and commit packages.lock.json so NuGet restores are repeatable.

Tests18pt80

Test files detected (Examples/UICatalog/Scenarios/TableViewTest.cs).

CI/CD14pt85

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

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (Examples/ScenarioRunner/ScenarioRunner.csproj).

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)
  • 779
    Forks
  • 66
    Releaseslatest 4y ago

Community

  • 87% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 11,084
    Watchers

Responsiveness

  • 29d 20h
    Median issue response
  • 2d 8h
    Median PR merge time
  • 54
    Open issues
Repository files42 root entries
  • .claude
  • .config
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/build-validation.yml).
    Good: Dependabot covers 2 ecosystems (github-actions, nuget). Dependencies stay current.
    Good: Issue or PR templates present.
  • .tg-docs
  • .vscode
  • docfx
  • Examples
    Good: Test files detected (Examples/UICatalog/Scenarios/TableViewTest.cs).
    Good: Environment pinned via Examples/UICatalog/Dockerfile.
    Good: Dependency manifest found (Examples/ScenarioRunner/ScenarioRunner.csproj).
  • Scripts
  • specs
  • Terminal.Gui
  • Terminal.Gui.Analyzers.Internal
  • Terminal.Gui.Interop.Spectre
  • Tests
  • .aider.md
  • .cursorrules
  • .dockerignore
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .vsconfig
  • .windsurfrules
  • AGENTS.md
  • ai-v2-primer.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codecov.yml
  • 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.
    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.
  • Directory.Build.props
  • Directory.Packages.props
  • GitVersion.yml
  • global.json
  • LICENSE
    Good: Licensed under MIT.
  • llms.txt
  • nuget.config
  • pull_request_template.md
  • 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.
  • Terminal.sln.DotSettings
  • Terminal.sln.ToDo.DotSettings
  • Terminal.slnx
  • testenvironments.json
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/gui-cs/terminal.gui)](https://www.repo-grade.com/report/gui-cs/terminal.gui)

More graded C# repos