xpdota/event-trigger

0

/ 100

Documentation72
Engineering54
Health94
Java118Other1d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

Comprehensive FFXIV Overlays, Triggers, Dot Tracker, Log Analysis, and more in an easy-to-use tool

Documentation

72

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.

README12pt75

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

54

Linting and formatting5pt0

No Java/Kotlin linter configured.

→ Add Checkstyle or Spotless for Java formatting, or ktlint/Detekt for Kotlin. Run it via Maven/Gradle or as a CI step.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

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.

Tests18pt80

Test files detected (easytriggers/src/test).

CI/CD14pt85

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

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (pom.xml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 35
    Forks
  • 20
    Releaseslatest 4y ago

Community

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

Responsiveness

  • 4h
    Median issue response
  • <1h
    Median PR merge time
  • 48
    Open issues
Repository files23 root entries
  • .github
    Good: CI is configured (.github/workflows/clean_branches.yml).
  • .idea
    Issue: Build artifacts or local files may be committed (.idea/codeStyles) (−40 pts).Fix: Remove them and add to .gitignore.
  • act-stub-plugin-assembly
  • actimport
  • easytriggers
    Good: Test files detected (easytriggers/src/test).
  • groovy-sandboxing
  • launcher
  • persistence
  • plugins
  • postnamazu-support
  • reevent
  • telesto-support
  • testutils
  • timelines
  • trigger-support
  • triggers
  • xivdata
  • xivsupport
  • .gitignore
    Good: .gitignore present.
  • libjawt.so
  • LICENSE
    Good: Licensed under Other.
  • pom.xml
    Good: Dependency manifest found (pom.xml).
  • README.md
    Good: README is present.
    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.
    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.