dfeo/tranformadores

0

/ 100

Documentation19
Engineering67
Health53
PHP09y ago
Grade a repo

Lots of room to improve. Start with a README and CI.

Documentation

19

README12pt0

README is present.

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

Contributing guide5pt0

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.

License6pt100

A license file is present.

Engineering

67

Linting and formatting5pt0

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.

Issue and PR templates6pt0

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.

Reproducibility6pt70

Lockfile present (es/clases/composer.lock). Installs are reproducible.

Tests18pt80

Test files detected (es/clases/PHPMailer/test).

CI/CD14pt100

CI is configured (es/clases/PHPMailer/.travis.yml).

Project health

53

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Repository metadata5pt40

No repository description set on GitHub (−60 pts).

→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (es/clases/PHPMailer/composer.json).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 6h
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files4 root entries
  • es
    Good: A license file is present.
    Good: Test files detected (es/clases/PHPMailer/test).
    Good: CI is configured (es/clases/PHPMailer/.travis.yml).
    Good: Lockfile present (es/clases/composer.lock). Installs are reproducible.
    Good: Dependency manifest found (es/clases/PHPMailer/composer.json).
    Issue: Build artifacts or local files may be committed (es/public/fonts/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • formulario
  • .gitignore
    Good: .gitignore present.
  • README.md
    Good: README is present.
    Issue: README is very short (−20 pts). 400+ characters earns +10 pts; 1,500+ earns +20 pts.Fix: Add an Overview, Install, Usage, and Contributing section at minimum.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown 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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.