dbos-inc/dbos-transact-py

0

/ 100

Documentation84
Engineering80
Health98
Python1,431MIT1d ago
Grade a repo

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

Database-Backed Durable Python Workflows

Documentation

84

Contributing guide5pt61

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt80

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

80

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 (pdm.lock). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/chaos-test.yml).

Tests18pt100

Test files detected (chaos-tests/conftest.py).

Linting and formatting5pt100

Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).

Project health

98

Dependency manifest6pt93

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)
  • 73
    Forks
  • 71
    Releaseslatest 1y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,431
    Watchers

Responsiveness

  • 19h
    Median issue response
  • <1h
    Median PR merge time
  • 3
    Open issues
Repository files16 root entries
  • .github
    Good: CI is configured (.github/workflows/chaos-test.yml).
  • chaos-tests
    Good: Test files detected (chaos-tests/conftest.py).
  • dbos
  • tests
  • version
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • .pydocstyle
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • DEVELOPING.md
  • LICENSE
    Good: Licensed under MIT.
  • make_release.py
  • pdm.lock
    Good: Lockfile present (pdm.lock). Installs are reproducible.
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • pyrightconfig.test.json
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.