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

UniGetUI: The Graphical Interface for your package managers. Could be terribly described as a package manager manager to manage your package managers

Documentation

81

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt80

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

78

Reproducibility6pt12

No dependency lockfile found (−70 pts).

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

Tests18pt80

Test files detected (src/UniGetUI.Core.Classes.Tests/ObservableQueueTests.cs).

CI/CD14pt85

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

Linting and formatting5pt100

.NET formatting configured (src/.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (InstallerExtras/MsiCreator/MsiInstallerWrapper.sln).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files26 root entries
  • .agents
  • .claude
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/build-release.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • configuration.winget
  • docs
  • InstallerExtras
    Good: Dependency manifest found (InstallerExtras/MsiCreator/MsiInstallerWrapper.sln).
  • media
  • package
  • scripts
  • src
    Good: Test files detected (src/UniGetUI.Core.Classes.Tests/ObservableQueueTests.cs).
    Good: .NET formatting configured (src/.editorconfig).
  • testing
  • WebBasedData
  • .deepsource.toml
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • CLAUDE.md
  • 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.
    Good: Contributing guide describes code style expectations.
    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.
  • global.json
  • LICENSE
    Good: Licensed under MIT.
  • 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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • SECURITY.md
    Good: Security policy present.
  • TRANSLATION.md
  • UniGetUI.iss