Getting some notice. Tests and CI would be the fastest wins.
Nova versão do site do projeto Visão Libertária
Documentation
51
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
63
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 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).
Lockfile present (composer.lock). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Project health
100
Dependency manifest found (composer.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 13Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 55Watchers
Responsiveness
- 1d 2hMedian issue response
- 10hMedian PR merge time
- 14Open issues
Repository files22 root entries
- .docker
- .githubGood: CI is configured (.github/workflows/ci.yml).
- app
- public
- tests
- writable
- .gitignoreGood: .gitignore present.
- .htaccess
- builds
- composer.jsonGood: Dependency manifest found (composer.json).
- composer.lockGood: Lockfile present (composer.lock). Installs are reproducible.
- docker-compose.yml
- DockerfileGood: Environment pinned via Dockerfile.
- env
- env.docker
- index.php
- LICENSEGood: Licensed under MIT.
- Makefile
- phpunit.xml.distGood: Test files detected (phpunit.xml.dist).
- preload.php
- README.mdGood: 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.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.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.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.
- spark