zatosource/zato
Grade a repo

0

/ 100

GradeC

Good community traction and solid fundamentals. Nearly in the top tier.

ESB, SOA, REST, APIs and Cloud Integrations in Python

Documentation76
Engineering60
Health100
Python1,010AGPL-3.0today

Documentation

76

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt72

CONTRIBUTING guide found.

README12pt90

README is present.

License6pt100

Licensed under AGPL-3.0.

Engineering

60

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/CD14pt40

CI is configured (.github/workflows/zato-compile.yml).

Reproducibility6pt70

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

Tests18pt80

Test files detected (code/tests).

Linting and formatting5pt100

Linter or formatter configured (code/ruff.toml).

Project health

100

Dependency manifest6pt100

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

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,010
    Watchers

Responsiveness

  • -
    Median issue response
  • 22h
    Median PR merge time
  • 0
    Open issues
Repository files8 root entries
  • .github
    Good: CI is configured (.github/workflows/zato-compile.yml).
  • code
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Test files detected (code/tests).
    Good: Linter or formatter configured (code/ruff.toml).
    Good: Lockfile present (code/requirements.txt). Installs are reproducible.
  • .gitignore
    Good: .gitignore present.
  • .post-commit.sh
  • LICENSE.txt
    Good: Licensed under AGPL-3.0.
  • Makefile
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.