ophian/styx
Grade a repo

62

/ 100

GradeD

A workable base with real gaps. Start with CI and a reproducible setup.

Higher than 46% of 5,156 graded repos

Serendipity Styx Edition - Styx is what Serendipity should be!

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (82).

See your top fixes
Now
D
62
Potential
B
82

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

    If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

  3. 3
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

  4. 4
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

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

72

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt75

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

A license file is present.

Engineering

40

CI/CD14pt0

No CI configuration detected in this repository.

If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

Commit composer.lock so Composer installs are repeatable.

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Tests18pt80

Test files detected (bundled-libs/tests).

Linting and formatting5pt100

PHP linting configured (bundled-libs/voku/simple-cache/phpstan.neon).

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

Activity, community, and responsiveness at scan time

Activity

  • 15 / 95
    Commits (30d / 90d)
  • 0
    Forks
  • 74
    Releaseslatest 8y ago

Community

  • 28% - Weak
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 9
    Watchers

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 0
    Open issues
Repository files26 root entries
  • archives
  • bundled-libs
    Good: A license file is present.
    Good: Test files detected (bundled-libs/tests).
    Good: PHP linting configured (bundled-libs/voku/simple-cache/phpstan.neon).
    Good: Security policy present.
  • deployment
  • docs
  • include
  • lang
  • plugins
  • sql
  • templates
  • templates_c
  • tests
  • uploads
  • .gitignore
    Good: .gitignore present.
  • checksums.inc.php
  • comment.php
  • composer.json
    Good: Dependency manifest found (composer.json).
  • exit.php
  • index.php
  • README.markdown
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
  • rss.php
  • serendipity_admin_image_selector.php
  • serendipity_admin.php
  • serendipity_config.inc.php
  • serendipity_xmlrpc.php
  • serendipity.css.php
  • wfwcomment.php
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/ophian/styx)](https://www.repo-grade.com/report/ophian/styx)

More graded PHP repos