Polished and well engineered. Punching above its star count.

๐Ÿ“Š A monitoring app which creates a server info dashboard for admins

Documentation

93

Contributing guide5pt72

CONTRIBUTING guide found.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under AGPL-3.0.

Engineering

91

Tests18pt80

Test files detected (tests).

Reproducibility6pt90

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

CI/CD14pt100

CI is configured (.github/workflows/lint-php-cs.yml).

Linting and formatting5pt100

PHP linting configured (psalm.xml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (composer.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files22 root entries
  • .github
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (โˆ’28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: CI is configured (.github/workflows/lint-php-cs.yml).
    Good: Dependabot covers 2 ecosystems (composer, composer). Dependencies stay current.
    Good: Issue or PR templates present.
  • .tx
  • appinfo
  • css
  • img
  • js
  • l10n
  • lib
  • LICENSES
  • templates
  • tests
    Good: Test files detected (tests).
  • vendor-bin
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • .php-cs-fixer.dist.php
  • AUTHORS.md
  • composer.json
    Good: Dependency manifest found (composer.json).
  • composer.lock
    Good: Lockfile present (composer.lock). Installs are reproducible.
  • COPYING
  • psalm.xml
    Good: PHP linting configured (psalm.xml).
  • 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.
  • REUSE.toml