microsoft/terminal

0

/ 100

Documentation91
Engineering68
Health100
C++103,653MIT5d ago
Grade a repo

Industry-defining adoption. A few engineering gaps, but the community carries it.

The new Windows Terminal and the original Windows console host, all in the same place!

Documentation

91

Contributing guide5pt85

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

68

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

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

Tests18pt80

Test files detected (src/cascadia/WindowsTerminal_UIATests/SmokeTests.cs).

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 (Scratch.sln).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files40 root entries
  • .config
  • .github
    Good: CI is configured (.github/workflows/addToProject.yml).
    Good: Issue or PR templates present.
  • .nuget
  • .vscode
  • build
  • dep
  • doc
  • oss
  • policies
  • res
  • samples
  • scratch
  • src
    Good: Test files detected (src/cascadia/WindowsTerminal_UIATests/SmokeTests.cs).
  • tools
  • .clang-format
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .vsconfig
  • .wt.json
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • common.openconsole.props
  • conhost.slnf
  • consolegit2gitfilters.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.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • custom.props
  • Directory.Build.props
  • Directory.Build.targets
  • dirs
  • LICENSE
    Good: Licensed under MIT.
  • NOTICE.md
  • NuGet.Config
  • OpenConsole.slnx
  • 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.
    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.
    Good: README documents how to run the project.
  • Scratch.sln
    Good: Dependency manifest found (Scratch.sln).
  • SECURITY.md
    Good: Security policy present.
  • SUPPORT.md
  • vcpkg.json
  • XamlStyler.json