louisbgl/brawl-stats
Grade a repo

0

/ 100

GradeD

Early stage. Tests, CI, and a strong README would raise this score quickly.

Brawl Stars stats tracker

Documentation54
Engineering55
Health93
JavaScript6today

Documentation

54

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

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.

README12pt70

README is present.

Install and run instructions9pt100

README documents how to install the project.

Engineering

55

Linting and formatting5pt0

No linter or formatter configured.

→ Add [tool.ruff] to pyproject.toml. Ruff handles linting and formatting in one tool and replaces flake8, isort, and black.

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.

CI/CD14pt57

CI is configured (.github/workflows/collect-battlelogs.yml).

Tests18pt80

Test files detected (testing/test_api.py).

Reproducibility6pt80

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

Project health

93

Dependency manifest6pt79

Dependency manifest found (pyproject.toml).

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)
  • 1
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 6
    Watchers

Responsiveness

  • 1h
    Median issue response
  • -
    Median PR merge time
  • 1
    Open issues
Repository files25 root entries
  • .github
    Good: CI is configured (.github/workflows/collect-battlelogs.yml).
  • assets
  • css
  • data
  • docs
  • js
  • proxy
  • src
  • testing
    Good: Test files detected (testing/test_api.py).
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • .nojekyll
  • .python-version
    Good: Environment pinned via .python-version.
  • CLAUDE.md
  • collect_battlelogs.py
  • collect_data.py
  • collect-battlelogs.sh
  • collect-snapshots.sh
  • favicon.png
  • generate_achievements.py
  • index.html
  • migrate_snapshots.py
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    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.
  • uv.lock
    Good: Lockfile present (uv.lock). Installs are reproducible.