owlchester/kanka

0

/ 100

Documentation84
Engineering86
Health100
PHP340Other1d ago
Grade a repo

Polished and well engineered. Punching above its star count.

Worldbuilding and RPG campaign management tool

Documentation

84

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.

README12pt75

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

86

Tests18pt80

Test files detected (app/Console/Commands/Tests).

Reproducibility6pt80

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

CI/CD14pt85

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

Linting and formatting5pt100

PHP linting configured (.editorconfig).

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)
  • 84
    Forks
  • 64
    Releaseslatest 6y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 340
    Watchers

Responsiveness

  • —
    Median issue response
  • 1d 18h
    Median PR merge time
  • 4
    Open issues
Repository files46 root entries
  • .claude
    Good: Security policy present.
  • .github
    Good: CI is configured (.github/workflows/lint.yml).
    Good: Issue or PR templates present.
  • .mariadb
  • .nginx
  • app
    Good: Test files detected (app/Console/Commands/Tests).
  • bootstrap
  • config
  • database
  • docker
  • docs
    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.
  • lang
  • public
  • resources
  • routes
  • storage
  • tests
  • .dockerignore
  • .editorconfig
    Good: PHP linting configured (.editorconfig).
  • .env.example
  • .env.testing
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .jshintrc
  • .mcp.json
  • .phpactor.json
  • artisan
  • boost.json
  • CLAUDE.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.
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • larastan.php
  • LICENSE
    Good: Licensed under Other.
  • package.json
  • phpcs.xml
  • phpmd_ruleset.xml
  • phpstan.neon
  • phpunit.xml
  • pint.json
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • server.php
  • sonar-project.properties
  • tailwind.config.js
  • vite.config.js
  • yarn.lock