chocolatey/choco
Grade a repo

71

/ 100

GradeC

Solid engineering. The biggest lever is CI.

Top 45% of 5,156 graded repos

Chocolatey - the package manager for Windows

Documentation93
Engineering46
Health100
C#11,471Other19d ago

Top fixes

Highest-impact changes first, ranked by point weight

16 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 step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

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

93

Contributing guide5pt72

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

46

Linting and formatting5pt0

No .NET formatter configured.

→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

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

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

CI/CD14pt57

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

Tests18pt80

Test files detected (tests).

Project health

100

Dependency manifest6pt100

Dependency manifest found (src/Chocolatey.PowerShell/Chocolatey.PowerShell.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

  • 2 / 12
    Commits (30d / 90d)
  • 961
    Forks
  • 45
    Releaseslatest 3y ago

Community

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

Responsiveness

  • 493d 4h
    Median issue response
  • 2d 10h
    Median PR merge time
  • 516
    Open issues
Repository files44 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
  • .notifications
  • .teamcity
  • .templates
  • .vscode
  • docker
  • docs
  • lib
  • nuspec
  • src
    Good: Dependency manifest found (src/Chocolatey.PowerShell/Chocolatey.PowerShell.csproj).
  • tests
    Good: Test files detected (tests).
  • tools
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • build.bat
  • build.debug.bat
  • build.debug.sh
  • build.official.bat
  • build.official.sh
  • build.ps1
  • build.sh
  • cake.config
  • CHANGELOG_LICENSED.md
  • CHANGELOG.md
  • chocolatey.snk
  • COMMITTERS.md
  • 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.
    Good: Contributing guide includes code examples.
  • formatting-settings.psd1
  • GitReleaseManager.yaml
  • GitVersion.yml
  • Invoke-AuthedTests.ps1
  • Invoke-Tests.ps1
  • LICENSE
    Good: Licensed under Other.
  • NOTICE
  • NuGet.config
  • 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.
  • recipe.cake
  • ScriptFormat.Tests.ps1
  • setup.cmd
  • setup.ps1
  • TESTING.md
  • Update-7zipVersion.ps1
  • update-cmdlet-documentation.ps1
  • update-nuget-client.ps1
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/chocolatey/choco)](https://www.repo-grade.com/report/chocolatey/choco)

More graded C# repos