Decent start, but looks inactive. Recent activity attracts contributors.
Just In Time image manipulation (GD, Imagick, imagemagick) with integration for laravel 4
Documentation
78
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.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
58
No PHP linter or static analysis tool configured.
→ Add PHP_CodeSniffer (phpcs.xml) for style or PHPStan (phpstan.neon) for static analysis. Run either in CI.
No dependency lockfile found (−70 pts).
→ Commit composer.lock so Composer installs are repeatable.
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.
Test files detected (phpunit.xml.dist).
CI is configured (.travis.yml).
Project health
75
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
Dependency manifest found (composer.json).
Repository has a description.
.gitignore present.
Repository files8 root entries
- src
- tests
- .gitignoreGood: .gitignore present.
- .travis.ymlGood: CI is configured (.travis.yml).
- composer.jsonGood: Dependency manifest found (composer.json).
- LICENSE.mdGood: Licensed under MIT.
- phpunit.xml.distGood: Test files detected (phpunit.xml.dist).
- README.mdGood: 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.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.