dagster-io/dagsterNew scan
81/ 100 · B

Popular and well-maintained. A little polish away from elite status.

An orchestration platform for the development, production, and observation of data assets.

Python15,685 starsApache-2.0updated 4d ago
DocumentationREADME, setup, examples, license
76
EngineeringTests, CI, linting, lockfiles
88
Project healthDescription, activity, stars, deps
72

What to fix first

The highest-impact improvements for this repo.

  1. 1
    CI/CD
    EngineeringWarning

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  2. 2
    CI/CD
    EngineeringInfo

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  3. 3
    CI/CD
    EngineeringInfo

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

Detailed breakdown

Documentation

76
  • README80
    • README is present.
    • README is well structured with multiple sections.
    • No screenshots or images in the README (−20 pts).Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    • README has code examples.
    • README links to a live demo or deployed app.
    • README includes status badges.
  • Install and run instructions55
    • No install instructions found in the README (−45 pts).Add a section showing how to install dependencies.
    • README documents how to run the project.
    • .env.example is present. Contributors can see exactly which env vars to set.
  • License100
    • Licensed under Apache-2.0.
  • Contributing guide75
    • CONTRIBUTING guide or docs directory present.
    • Code of conduct present.

Engineering

88
  • Tests100
    • Test files detected (.buildkite/buildkite-shared/buildkite_shared/test_utils.py).
    • Pytest configured via [tool.pytest.ini_options] in pyproject.toml with test files present.
  • CI/CD72

    Not applicable?

    • CI is configured (.github/workflows/build-docs.yml).
    • The CI workflow does not appear to run any tests (−28 pts).Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
    • CI runs on pull requests, not just on pushes to main.
    • CI workflow runs a lint or format check.
    • Optional: add type checking to CI.Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
    • Optional: report test coverage in CI.Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
  • Linting and formatting60
    • Linter or formatter configured (config/ruff.toml).
  • Reproducibility100
    • Lockfile present (uv.lock). Installs are reproducible.
    • Environment pinned via examples/deploy_docker/docker-compose.yml.
    • Dependabot covers 2 ecosystems (npm, pip). Dependencies stay current.
    • Dependabot is not configured for GitHub Actions.Add a `package-ecosystem: github-actions` entry to keep workflow action versions up to date.
  • Issue and PR templates100
    • Issue or PR templates present.
    • Security policy present.

Project health

72
  • Dependency manifest55
    • Dependency manifest found (pyproject.toml).
  • Repository metadata70
    • Repository has a description.
    • Primary language detected: Python.
  • Activity100
    • Actively maintained (pushed within the last month).
    • 15,685 stars.
  • Housekeeping60
    • .gitignore present.
    • Build artifacts or local files may be committed (python_modules/dagster/dagster_tests/general_tests/grpc_tests/.env) (−40 pts).Remove them and add to .gitignore.
Repository files37 root entries
  • .buildkite
    Good: Test files detected (.buildkite/buildkite-shared/buildkite_shared/test_utils.py).
  • .claude
  • .erk
  • .github
    Good: CONTRIBUTING guide or docs directory present.
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/build-docs.yml).
    Good: Dependabot covers 2 ecosystems (npm, pip). Dependencies stay current.
    Good: Issue or PR templates present.
  • .tmp
  • .vscode
  • config
    Good: Linter or formatter configured (config/ruff.toml).
  • docs
    Good: Security policy present.
  • examples
    Good: Environment pinned via examples/deploy_docker/docker-compose.yml.
  • helm
  • integration_tests
  • js_modules
  • python_modules
    Warning: Build artifacts or local files may be committed (python_modules/dagster/dagster_tests/general_tests/grpc_tests/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • scripts
  • ty
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitpod.yml
  • .mcp.json
  • .pre-commit-config.yaml
  • .prettierignore
  • azure-pipelines.yml
  • CHANGES.md
  • CLAUDE.md
  • conftest.py
  • copy.bara.sky
  • justfile
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • MIGRATION.md
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Warning: 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.
    Warning: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • RUN_API_IMPLEMENTATION_PLAN.md
  • RUN_API_SPECIFICATION.md
  • TODO.md
  • uv.lock
    Good: Lockfile present (uv.lock). Installs are reproducible.