seafoam-labs/shelly-alpm
Grade a repo

81

/ 100

GradeC

Solid engineering. The biggest lever is CI.

Top 39% of 5,156 graded repos

Pacman alternative for ArchLinux, designed with you in mind.

Documentation90
Engineering68
Health68
Zig1,160GPL-3.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

14 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
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

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

90

Contributing guide5pt80

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under GPL-3.0.

Engineering

68

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

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

Tests18pt80

Test files detected (Shelly.PackageManager/zig-pkg/goose-1.0.0-e9MzMGKcAgD7vlp_acJYt6g430wQcrAxUKWHEEF0_Hcc/src/tests).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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)
  • 93
    Forks
  • 104
    Releaseslatest 9mo ago

Community

  • 62% - Fair
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 1,160
    Watchers

Responsiveness

  • 4h
    Median issue response
  • <1h
    Median PR merge time
  • 42
    Open issues
Repository files31 root entries
  • .github
    Good: CI is configured (.github/workflows/build-and-publish.yml).
    Good: Issue or PR templates present.
  • .zed
  • assets
  • docs
  • scripts
  • Shelly.Cli.Zig
  • Shelly.Diagnostics
  • Shelly.Flatpak.Backend
  • Shelly.Http
  • Shelly.Key
  • Shelly.Notifications.Zig
  • Shelly.PackageManager
    Good: Test files detected (Shelly.PackageManager/zig-pkg/goose-1.0.0-e9MzMGKcAgD7vlp_acJYt6g430wQcrAxUKWHEEF0_Hcc/src/tests).
  • Shelly.Tui
  • Shelly.Ui.Gtk
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • com.shellyorg.shelly-notifications.desktop
  • com.shellyorg.shelly.desktop
  • 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.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • LICENSE
    Good: Licensed under GPL-3.0.
  • MANUAL_TESTING.md
  • PKGBUILD
  • PKGBUILD-bin
  • PKGBUILD-cli
  • PKGBUILD-git
  • 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.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • shelly_banner.png
  • shelly-flatpak-integrate
  • shellybuild.conf
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/seafoam-labs/shelly-alpm)](https://www.repo-grade.com/report/seafoam-labs/shelly-alpm)

More graded Zig repos