subtitleedit/subtitleedit
Grade a repo

0

/ 100

GradeD

Strong community interest, but docs and engineering haven't caught up to the hype.

Top 48% of 5,156 graded repos

the subtitle editor :)

Documentation58
Engineering62
Health100
C#13,211MIT1mo 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 C (77).

See your top fixes
Now
D
68
Potential
C
77

Top fixes

Highest-impact changes first, ranked by point weight

15 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

58

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

Install and run instructions9pt45

README documents how to install the project.

README12pt70

README is present.

License6pt100

Licensed under MIT.

Engineering

62

Linting and formatting5pt0

No .NET formatter configured.

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

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.

Reproducibility6pt70

Lockfile present (src/ui/packages.lock.json). Installs are reproducible.

Tests18pt80

Test files detected (tests).

CI/CD14pt85

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

Project health

100

Dependency manifest6pt100

Dependency manifest found (SubtitleEdit.sln).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files18 root entries
  • .github
    Good: CI is configured (.github/workflows/build-flatpak.yml).
  • Dictionaries
  • docs
  • installer
  • Ocr
  • src
    Good: Lockfile present (src/ui/packages.lock.json). Installs are reproducible.
  • tests
    Good: Test files detected (tests).
  • Themes
  • .gitignore
    Good: .gitignore present.
  • appveyor.yml
  • change-log.txt
  • Changelog.txt
  • Directory.Build.props
  • LICENSE
    Good: Licensed under MIT.
  • make-installer.bat
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • SubtitleEdit.sln
    Good: Dependency manifest found (SubtitleEdit.sln).
  • SubtitleEdit.sln.DotSettings
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/subtitleedit/subtitleedit)](https://www.repo-grade.com/report/subtitleedit/subtitleedit)

More graded C# repos