paycal-technologies/paycal

0

/ 100

Documentation76
Engineering93
Health100
PHP0Other5d ago
Grade a repo

Polished work that hasn't found its audience yet.

PayCal core infrastructure and utilities

Documentation

76

Install and run instructions9pt55

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

→ Add a section showing how to install dependencies.

Contributing guide5pt77

CONTRIBUTING guide found.

README12pt80

README is present.

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
  • 3
    Releaseslatest 5d ago

Community

  • 50% - Fair
    Community health
  • —
    authors own >50% of commits
  • 0
    Watchers

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 1
    Open issues
Repository files25 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.
  • config
  • copilot-scripts
  • docs
  • githooks
  • html
    Good: Test files detected (html/api/tests).
  • scripts
  • strings
  • templates
  • tests
  • tools
  • vendor
    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: Code of conduct present.
    Good: Environment pinned via vendor/maennchen/zipstream-php/.tool-versions.
    Good: Security policy present.
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • .gitleaks.toml
  • composer.json
    Good: Dependency manifest found (composer.json).
  • composer.lock
    Good: Lockfile present (composer.lock). Installs are reproducible.
  • eslint.config.js
    Good: PHP linting configured (eslint.config.js).
  • LICENSE.txt
    Good: Licensed under Other.
  • package.json
  • phpstan.neon
  • phpunit.public.xml
  • phpunit.xml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    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.
    Good: README documents how to run the project.
  • VERSION