kdeldycke/meta-package-manager
Grade a repo

86

/ 100

GradeA

Excellent work. The main thing left to polish is a contributing guide.

Top 10% of 5,156 graded repos

🎁 snapshot every package on your machine to one file, restore it on a new one

Documentation91
Engineering91
Health98
Python610GPL-2.02d ago

Top fixes

Highest-impact changes first, ranked by point weight

11 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
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  3. 3
    Reproducibility6pt

    Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.

  4. 4
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry, or a renovate.json, so dependencies are updated automatically.

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 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

91

Reproducibility6pt70

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

Tests18pt85

Test files detected (tests).

CI/CD14pt100

CI is configured (.github/workflows/check-opensuse-spec.yaml).

Linting and formatting5pt100

Linter or formatter configured (gnome-shell/eslint.config.mjs).

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)
  • 48
    Forks
  • 95
    Releaseslatest 5y ago

Community

  • 85% - Good
    Community health
  • -
    authors own >50% of commits
  • 610
    Watchers

Responsiveness

  • 1034d 17h
    Median issue response
  • 1d 9h
    Median PR merge time
  • 20
    Open issues
Repository files17 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/check-opensuse-spec.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.
    Good: Security policy present.
  • gnome-shell
    Good: Linter or formatter configured (gnome-shell/eslint.config.mjs).
  • 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.
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/kdeldycke/meta-package-manager)](https://www.repo-grade.com/report/kdeldycke/meta-package-manager)

More graded Python repos