flytohub/flyto-coreNew scan
99/ 100 · A

Polished and well engineered. Punching above its star count.

The open-source execution engine for AI agents. 412 modules, MCP-native, triggers, queue, versioning, metering.

Python275 starsApache-2.0updated today

Outstanding work. A score of 99/100 puts this repo in a very small tier of truly well-engineered open source projects.

DocumentationREADME, setup, examples, license
100
EngineeringTests, CI, linting, lockfiles
99
Project healthDescription, activity, stars, deps
100

What to fix first

The highest-impact improvements for this repo.

  1. 1
    CI/CD
    EngineeringInfo

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

  2. 2
    CI/CD
    EngineeringInfo

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

  3. 3
    Reproducibility
    EngineeringIssue

    Add additional package-ecosystem entries (especially github-actions) to keep all dependencies current.

Detailed breakdown

Documentation

100
  • README100
    • README is present.
    • README is well structured with multiple sections.
    • README includes screenshots or visuals. Great for first impressions.
    • README has code examples.
    • README links to a live demo or deployed app.
    • README includes status badges.
  • Install and run instructions100
    • README documents how to install the project.
    • 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 guide100
    • Contributing guide is detailed and thorough.
    • Contributing guide includes setup/install instructions.
    • Contributing guide describes code style expectations.
    • Contributing guide explains how to run tests.
    • Contributing guide describes the PR/review workflow.
    • Contributing guide includes code examples.
    • Code of conduct present.

Engineering

99
  • Tests100
    • Test files detected (examples/happy-test/test_figma.py).
    • Pytest is fully configured in pyproject.toml with testpaths and test files detected.
  • CI/CD100

    Not applicable?

    • CI is configured (.github/workflows/ci.yml).
    • CI workflow runs tests.
    • 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 formatting100
    • Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
  • Reproducibility92
    • Lockfile present (requirements.txt). Installs are reproducible.
    • Environment pinned via Dockerfile.
    • Dockerfile uses multi-stage builds (smaller, more secure images).
    • Dockerfile includes a HEALTHCHECK instruction.
    • Dockerfile runs as a non-root user.
    • Dependabot configured for pip.
    • Dependabot only covers one ecosystem (−8 pts). Covering 2+ ecosystems earns the full +20 pts.Add additional package-ecosystem entries (especially github-actions) to keep all dependencies current.
  • Issue and PR templates100
    • Issue or PR templates present.
    • Security policy present.

Project health

100
  • Dependency manifest100
    • Dependency manifest found (pyproject.toml).
    • pyproject.toml has a [project] table with package metadata.
    • pyproject.toml includes a description.
    • pyproject.toml specifies requires-python, preventing installs on incompatible versions.
    • pyproject.toml has a [build-system] table. The package can be built and published.
  • Repository metadata100
    • Repository has a description.
    • Primary language detected: Python.
    • pyproject.toml [project] metadata is complete (description, authors, urls).
  • Activity100
    • Actively maintained (pushed within the last month).
    • 275 stars.
  • Housekeeping100
    • .gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 48
    Forks
  • 5
    Releaseslatest 23d ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 275
    Watchers

Responsiveness

  • 4h
    Median issue response
  • 3d 19h
    Median PR merge time
  • 2
    Open issues
Repository files46 root entries
  • .flyto
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot configured for pip.
    Good: Issue or PR templates present.
  • audit_report
  • demo
  • docs
  • examples
    Good: Test files detected (examples/happy-test/test_figma.py).
  • handoffs
  • out
  • plugin-template
  • scripts
  • src
  • tests
  • workflows
  • .dockerignore
  • .env.example
  • .flyto-rules.yaml
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • ARCHITECTURE.md
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • DECISIONS.md
  • demo.gif
  • demo.py
  • demo.tape
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MANIFEST.in
  • NOTICE
  • PROJECT.md
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • registry.json
  • requirements-integrations.txt
  • requirements.lock
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
  • ROADMAP.md
  • run_demo.sh
  • run.py
  • SECURITY.md
    Good: Security policy present.
  • server.json
  • setup.py
  • STATE.md
  • tasks.md