martineesmaa/vvceasy
Grade a repo

0

/ 100

GradeD

Popular for its size, but the engineering basics lag behind the interest.

Top 50% of 5,156 graded repos

VVCEasy provides ready prebuilt VVC (Versatile Video Codec) binaries & players. Simple, Easy, Encode and Decode.

Documentation91
Engineering37
Health100
Batchfile234MIT1mo 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 (87).

See your top fixes
Now
D
66
Potential
B
87

Top fixes

Highest-impact changes first, ranked by point weight

14 to address
  1. 1
    Tests18pt

    Add automated tests. They prove the code works and give contributors confidence to make changes.

  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

91

Contributing guide5pt60

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

37

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

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.

CI/CD14pt85

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (VVCEasy.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)
  • 24
    Forks
  • 12
    Releaseslatest 1y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 234
    Watchers

Responsiveness

  • 13h
    Median issue response
  • <1h
    Median PR merge time
  • 1
    Open issues
Repository files36 root entries
  • .github
    Good: CI is configured (.github/workflows/dotnet.yml).
    Good: Issue or PR templates present.
  • 7-Zip
    Good: Licensed under MIT.
  • AndroidVVC
  • assets
  • docs-old
  • FreeBSDVVC
  • HaikuVVC
  • INSTALLVLCPLUGIN
  • LAVFilters
  • LinuxVVC
  • MacOSVVC
  • OpenVVC
  • Screenshots
  • uvg266
  • VVDECWEBINSTALL
  • WindowsVVC
  • .gitignore
    Good: .gitignore present.
  • AUTHORS.md
  • BuildFFmpeg.sh
  • BuildVVC.sh
  • CHANGELOG
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    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.
  • FFMPEGVVC.md
  • LICENSE
  • MPV.md
  • Program.cs
  • 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.
  • SOCIALMEDIA.md
  • THANKS.md
  • VVC.md
  • VVCEasy_compiler.iss
  • VVCEasy.266
  • VVCEasy.bat
  • VVCEasy.csproj
    Good: Dependency manifest found (VVCEasy.csproj).
  • wget.exe
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/martineesmaa/vvceasy)](https://www.repo-grade.com/report/martineesmaa/vvceasy)

More graded Batchfile repos