bcuninstaller/bulk-crap-uninstaller
Grade a repo

69

/ 100

GradeD

A workable base with real gaps. Start with CI and a reproducible setup.

Top 47% of 5,156 graded repos

Remove large amounts of unwanted applications quickly.

Documentation87
Engineering46
Health100
C#20,552Apache-2.03d ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (81).

See your top fixes
Now
D
69
Potential
B
81

Top fixes

Highest-impact changes first, ranked by point weight

17 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

87

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

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/ci.yaml).

Tests18pt80

Test files detected (source/BulkCrapUninstallerTests/ApplicationEntrySerializerTests.cs).

Project health

100

Dependency manifest6pt100

Dependency manifest found (source/BCU-console/BCU-console.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

  • 4 / 32
    Commits (30d / 90d)
  • 896
    Forks
  • 71
    Releaseslatest 9y ago

Community

  • 62% - Fair
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 20,552
    Watchers

Responsiveness

  • 7d 17h
    Median issue response
  • <1h
    Median PR merge time
  • 151
    Open issues
Repository files12 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yaml).
  • doc
  • installer
  • source
    Good: Test files detected (source/BulkCrapUninstallerTests/ApplicationEntrySerializerTests.cs).
    Good: Dependency manifest found (source/BCU-console/BCU-console.csproj).
  • .gitignore
    Good: .gitignore present.
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • Licence.txt
    Good: Licensed under Apache-2.0.
  • NOTICE
  • PrivacyPolicy.txt
  • publish.bat
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
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/bcuninstaller/bulk-crap-uninstaller)](https://www.repo-grade.com/report/bcuninstaller/bulk-crap-uninstaller)

More graded C# repos