Solid foundation. Invest in docs and CI to grow from here.

Switch platforms, keep your people

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 CC0-1.0.

Engineering

67

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.

Reproducibility6pt70

Lockfile present (requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (tests).

CI/CD14pt100

CI is configured (.circleci/config.yml).

Project health

91

Dependency manifest6pt71

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

Community

  • Community health
  • authors own >50% of commits
  • 25
    Watchers

Responsiveness

  • 14d 15h
    Median issue response
  • <1h
    Median PR merge time
  • 18
    Open issues
Repository files15 root entries
  • .circleci
    Good: CI is configured (.circleci/config.yml).
  • static
  • templates
  • tests
    Good: Test files detected (tests).
  • .gcloudignore
  • .gitignore
    Good: .gitignore present.
  • app.yaml
  • bounce.py
  • config.py
  • LICENSE
    Good: Licensed under CC0-1.0.
  • oauth_dropins_fonts
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README.md
    Good: README is present.
    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.
    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.
  • requirements.pinned.txt
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.