josefnemec/playnite

0

/ 100

Documentation76
Engineering80
Health100
C#13,297MIT29d ago
Grade a repo

Popular and well-maintained. A little polish away from elite status.

Video game library manager with support for wide range of 3rd party libraries and game emulation support, providing one unified interface for your games.

Documentation

76

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.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

80

Reproducibility6pt0

No dependency lockfile found (−70 pts).

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

Tests18pt80

Test files detected (source/Tests).

CI/CD14pt100

CI is configured (appveyor.yml).

Linting and formatting5pt100

.NET formatting configured (source/.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (source/Playnite.DesktopApp/Playnite.DesktopApp.csproj).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files11 root entries
  • .github
    Good: Issue or PR templates present.
  • build
  • media
  • references
  • source
    Good: Test files detected (source/Tests).
    Good: .NET formatting configured (source/.editorconfig).
    Good: Dependency manifest found (source/Playnite.DesktopApp/Playnite.DesktopApp.csproj).
  • tests
  • .gitignore
    Good: .gitignore present.
  • appveyor.yml
    Good: CI is configured (appveyor.yml).
  • crowdin.yml
  • LICENSE.md
    Good: Licensed under MIT.
  • README.md
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    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.