libresign/libresign
Grade a repo

80

/ 100

GradeB

Well engineered. The main gaps are setup instructions and CI.

Top 32% of 5,156 graded repos

Control how your documents get signed

Documentation60
Engineering85
Health100
PHP784AGPL-3.07d ago

Top fixes

Highest-impact changes first, ranked by point weight

13 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

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  4. 4
    README12pt

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

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

60

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

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.

README12pt85

README is present.

License6pt100

Licensed under AGPL-3.0.

Engineering

85

CI/CD14pt72

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

Tests18pt80

Test files detected (playwright/e2e/confetti-after-signing-policy.spec.ts).

Linting and formatting5pt100

PHP linting configured (.editorconfig).

Reproducibility6pt100

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

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

Activity, community, and responsiveness at scan time

Activity

  • 255 / 1595
    Commits (30d / 90d)
  • 121
    Forks
  • 218
    Releaseslatest 5y ago

Community

  • 100% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 784
    Watchers

Responsiveness

  • 125d 19h
    Median issue response
  • <1h
    Median PR merge time
  • 83
    Open issues
Repository files56 root entries
  • .devcontainer
    Good: Environment pinned via .devcontainer/docker-compose.yml.
  • .github
    Good: CI is configured (.github/workflows/lint-eslint.yml).
    Good: Dependabot covers 3 ecosystems (composer, npm, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .patches
  • .tx
  • .well-known
  • appinfo
  • composer
  • img
  • l10n
  • lib
  • LICENSES
  • playwright
    Good: Test files detected (playwright/e2e/confetti-after-signing-policy.spec.ts).
  • src
  • templates
  • tests
  • vendor-bin
  • .editorconfig
    Good: PHP linting configured (.editorconfig).
  • .eslintignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .l10nignore
  • .npmignore
  • .php-cs-fixer.dist.php
  • .prettierrc
  • 3rdparty
  • AGENTS.md
  • AUTHORS
  • babel.config.js
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • composer.json
    Good: Dependency manifest found (composer.json).
  • composer.lock
    Good: Lockfile present (composer.lock). Installs are reproducible.
  • CONTRIBUTING.md
    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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • COPYING
  • eslint.config.mjs
  • funding.json
  • Makefile
  • openapi-administration.json
  • openapi-full.json
  • openapi.json
  • package-lock.json
  • package.json
  • patches.json
  • patches.lock.json
  • playwright.config.ts
  • 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.
    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.
    Good: README includes status badges.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • rector.php
  • redocly.yaml
  • REUSE.toml
  • SECURITY.md
    Good: Security policy present.
  • stylelint.config.js
  • tsconfig.json
  • vite.config.mjs
  • vitest.config.js
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/libresign/libresign)](https://www.repo-grade.com/report/libresign/libresign)

More graded PHP repos