paycal-technologies/paycal
Grade a repo

93

/ 100

GradeA

Exemplary work. Strong across project hygiene, documentation, and engineering. It just hasn't found an audience yet.

Top 5% of 5,156 graded repos

Privacy-first work-hours, pay visibility, and payroll-adjacent reporting for workers and businesses.

Documentation99
Engineering93
Health100
PHP0Other22d ago

Outstanding. A score of 96/100 puts this repo in a very small tier of truly well-engineered projects.

Top fixes

Highest-impact changes first, ranked by point weight

2 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
    Contributing guide5pt

    Describe your linting/formatting rules and how to run them.

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

99

Contributing guide5pt97

Contributing guide is detailed and thorough.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

93

Tests18pt80

Test files detected (html/api/tests).

CI/CD14pt100

CI is configured (.github/workflows/javascript.yml).

Linting and formatting5pt100

PHP linting configured (eslint.config.js).

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

  • -
    Commits (30d / 90d)
  • 0
    Forks
  • 4
    Releaseslatest 1mo ago

Community

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

Responsiveness

  • -
    Median issue response
  • -
    Median PR merge time
  • 10
    Open issues
Repository files33 root entries
  • .github
    Good: CI is configured (.github/workflows/javascript.yml).
    Good: Dependabot covers 3 ecosystems (github-actions, composer, npm). Dependencies stay current.
    Good: Issue or PR templates present.
  • ai-notes
  • config
  • copilot-scripts
  • docs
  • examples
  • githooks
  • html
    Good: Test files detected (html/api/tests).
  • scripts
  • strings
  • templates
  • tests
  • tools
  • vendor
    Good: Environment pinned via vendor/maennchen/zipstream-php/.tool-versions.
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • .gitleaks.toml
  • .php-cs-fixer.php
  • 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
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
  • eslint.config.js
    Good: PHP linting configured (eslint.config.js).
  • LICENSE.txt
    Good: Licensed under Other.
  • package-lock.json
  • package.json
  • phpstan.neon
  • phpunit.public.xml
  • phpunit.xml
  • playwright.smoke.config.js
  • 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.
  • SECURITY.md
    Good: Security policy present.
  • VERSION
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/paycal-technologies/paycal)](https://www.repo-grade.com/report/paycal-technologies/paycal)

More graded PHP repos