microsoft/autogenNew scan
81/ 100 · B

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

A programming framework for agentic AI

Python58,946 starsCC-BY-4.0updated 2mo ago
DocumentationREADME, setup, examples, license
88
EngineeringTests, CI, linting, lockfiles
74
Project healthDescription, activity, stars, deps
87

What to fix first

The highest-impact improvements for this repo.

  1. 1
    CI/CD
    EngineeringInfo

    Add a lint step (e.g. `npm run lint`, `ruff check .`, `cargo clippy`) to catch style issues automatically.

  2. 2
    README
    DocumentationWarning

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  3. 3
    Install and run instructions
    DocumentationInfo

    Add a .env.example listing all required environment variables so contributors know what to set up.

Detailed breakdown

Documentation

88
  • 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 instructions90
    • README documents how to install the project.
    • README documents how to run the project.
    • If your project uses environment variables, add a .env.example listing them (+10 pts).Add a .env.example listing all required environment variables so contributors know what to set up.
  • License100
    • Licensed under CC-BY-4.0.
  • Contributing guide87
    • Contributing guide is detailed and thorough.
    • Contributing guide includes setup/install instructions.
    • Contributing guide lacks a code style section (−8 pts).Describe your linting/formatting rules and how to run them (e.g. npm run lint, ruff check .).
    • Contributing guide lacks a testing section (−8 pts).Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    • Contributing guide describes the PR/review workflow.
    • Contributing guide includes code examples.
    • Code of conduct present.

Engineering

74
  • Tests60
    • Test files detected (dotnet/test).
  • CI/CD85

    Not applicable?

    • CI is configured (.github/workflows/checks.yml).
    • CI workflow runs tests.
    • CI runs on pull requests, not just on pushes to main.
    • CI does not appear to run a linter (−15 pts).Add a lint step (e.g. `npm run lint`, `ruff check .`, `cargo clippy`) to catch style issues automatically.
    • CI runs type checking (tsc, mypy, cargo check, etc.).
    • CI reports or uploads test coverage.
    • CI tests across multiple environments or versions.
  • Linting and formatting60
    • Linter or formatter configured (dotnet/.editorconfig).
  • Reproducibility80
    • Lockfile present (python/packages/agbench/benchmarks/GAIA/Templates/MagenticOne/requirements.txt). Installs are reproducible.
    • Environment pinned via .devcontainer/Dockerfile.
    • No Dependabot config (adding it earns up to +20 pts).Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
  • Issue and PR templates100
    • Issue or PR templates present.
    • Security policy present.

Project health

87
  • Dependency manifest100
    • Dependency manifest found (python/packages/agbench/benchmarks/GAIA/Templates/MagenticOne/requirements.txt).
  • Repository metadata70
    • Repository has a description.
    • Primary language detected: Python.
  • Activity80
    • Actively maintained (pushed within 3 months).
    • 58,946 stars.
  • Housekeeping100
    • .gitignore present.
Repository files20 root entries
  • .azure
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/checks.yml).
    Good: Issue or PR templates present.
  • docs
  • dotnet
    Good: Test files detected (dotnet/test).
    Good: Linter or formatter configured (dotnet/.editorconfig).
  • protos
  • python
    Good: Lockfile present (python/packages/agbench/benchmarks/GAIA/Templates/MagenticOne/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (python/packages/agbench/benchmarks/GAIA/Templates/MagenticOne/requirements.txt).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • autogen-landing.jpg
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codecov.yml
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Info: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them (e.g. npm run lint, ruff check .).
    Info: 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.
    Good: Contributing guide includes code examples.
  • FAQ.md
  • LICENSE
    Good: Licensed under CC-BY-4.0.
  • LICENSE-CODE
  • 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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • SUPPORT.md
  • TRANSPARENCY_FAQS.md