Agent Friendly Code
← back to leaderboard

apache/seatunnelGitHub

https://github.com/apache/seatunnel
Stars:
9.7k
Language:
Java
Default branch:
dev
Last scored:
5h ago
Overall

At a glance

Rank
#228 of 371
#9 of 28 Java repos
Checks passed
7 of 16
Full list below
Best set up for
Gemini CLI
Score 74.7
Needs most work for
Aider
Biggest fix: .aider.conf.yml (+14.1 pts)

What it has

  • AGENTS.md / CLAUDE.md
  • CI configuration
  • Dependency manifest
  • GEMINI.md
  • License file

What it's missing

  • .aider.conf.yml
  • CONTRIBUTING guide
  • Cursor rules (.cursor/rules)
  • Linter / formatter config
  • .openhands/setup.sh

What to fix first

  1. 1
    Linter / formatter config
    Configure a linter/formatter (ESLint+Prettier, Biome, Ruff, rustfmt+clippy, golangci-lint) and commit the config.
    +7.9 pts
  2. 2
    CONTRIBUTING guide
    Add CONTRIBUTING.md describing branch naming, commit style, test commands, and the PR process.
    +5.3 pts
  3. 3
    Pre-commit / git hooks
    Set up pre-commit (.pre-commit-config.yaml), husky, or lefthook to run format+lint on every commit.
    +5.3 pts

Score for each AI agent

Each agent looks for different things in a repo, based on its own docs. Under each score are the three checks it cares about most.

Gemini CLI
74.7
GPT-5 Codex
72.0
Claude Code
70.8
Kimi CLI
70.7
Devin
69.2
Pi
69.0
Cursor
64.3
OpenHands
60.2
Aider
54.2

Similar repos

Scored for Claude Code. Same language and host as this repo, scoring near it.

All Java repos →

All checks

AGENTS.md / CLAUDE.md· 100% pass
Substantive (7510 chars)
AGENTS.md
.aider.conf.yml· 0% pass
No .aider.conf.yml at repo root
CI configuration· 100% pass
18 GitHub Actions workflow(s)
.github/workflows
CONTRIBUTING guide· 0% pass
No CONTRIBUTING file
Cursor rules (.cursor/rules)· 0% pass
No .cursor/rules/*.mdc or .cursorrules
Dependency manifest· 100% pass
Manifest present
pom.xml
Reproducible dev env· 70% pass
Has mvnw
mvnw
GEMINI.md· 100% pass
Substantive GEMINI.md (7510 chars)
GEMINI.md
License file· 100% pass
License present
LICENSE
Linter / formatter config· 0% pass
No linter/formatter config found
.openhands/setup.sh· 0% pass
No .openhands/setup.sh
Pre-commit / git hooks· 0% pass
No pre-commit / husky / lefthook found
README· 100% pass
README detailed (5812 chars)
README.md
Manageable size· 50% pass
3770 files — large
Test suite· 70% pass
Test files detected (seatunnel-cli/tests/test_benchmark_comparison.py)
seatunnel-cli/tests/test_benchmark_comparison.py
Type configuration· 100% pass
Typed language (Java)

Add a badge to your README

Paste this at the top of the README. It shows the score, and links back to this page.

Agent friendly score for github/apache/seatunnel
[![Agent Friendly](https://agentfriendlycode.com/api/badge/github/apache/seatunnel.svg)](https://agentfriendlycode.com/repo/github/apache/seatunnel)

Check the score on every pull request

Add this file to your repo. On each pull request, it posts one comment showing how the score changed and why. It runs in your own CI, with no outside server involved.

# .github/workflows/agent-friendly.yml
name: Agent-friendly score diff

on:
  pull_request:
    branches: [dev]

permissions:
  contents: read
  pull-requests: write

jobs:
  score-diff:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
        with:
          fetch-depth: 0
      - uses: hsnice16/agent-friendly-action@v0
        with:
          agents-badge-token: ${{ secrets.AGENTS_BADGE_TOKEN }}

Add AGENTS_BADGE_TOKENto the repo's secrets to turn the comment on. Without it, the action does nothing. Where do I add it?