0

/ 100

GradeB

Polished and well engineered. Punching above its star count.

๐ŸŽ wraps all package managers with a unifying CLI

Documentation

91

Contributing guide5pt58

Contributing guide is too short for full depth credit (โˆ’6 pts). 400+ words earns the full +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 GPL-2.0.

Engineering

79

CI/CD14pt57

CI is configured (.github/workflows/check-guix-deps.yaml).

Reproducibility6pt70

Lockfile present (uv.lock). Installs are reproducible.

Tests18pt85

Test files detected (tests).

Linting and formatting5pt100

Linter or formatter configured ([tool.mypy] in pyproject.toml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

98

Dependency manifest6pt93

Dependency manifest found (pyproject.toml).

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)
  • 49
    Forks
  • 87
    Releaseslatest 5y ago

Community

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

Responsiveness

  • 1034d 17h
    Median issue response
  • 1d 9h
    Median PR merge time
  • 21
    Open issues
Repository files16 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/check-guix-deps.yaml).
    Good: Issue or PR templates present.
  • docs
    Good: Licensed under GPL-2.0.
    Issue: Contributing guide is too short for full depth credit (โˆ’6 pts). 400+ words earns the full +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).
    Issue: Contributing guide lacks a PR workflow section (โˆ’8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • meta_package_manager
  • packaging
  • tests
    Good: Test files detected (tests).
  • .gitignore
    Good: .gitignore present.
  • .gitlab-ci.yml
  • .mailmap
  • changelog.md
  • citation.cff
  • claude.md
  • license
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • 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.
  • uv.lock
    Good: Lockfile present (uv.lock). Installs are reproducible.