← back to leaderboard

firecrawl/firecrawlGitHub

https://github.com/firecrawl/firecrawl
Stars:
190.5k
Language:
TypeScript
Default branch:
main
Last scored:
6h ago
Overall

At a glance

Rank
#347 of 371
#79 of 81 TypeScript repos
Checks passed
5 of 16
Full list below
Best set up for
GPT-5 Codex
Score 54.1
Needs most work for
Aider
Biggest fix: .aider.conf.yml (+14.1 pts)

What it has

  • AGENTS.md / CLAUDE.md
  • CI configuration
  • CONTRIBUTING guide
  • License file
  • README

What it's missing

  • .aider.conf.yml
  • Cursor rules (.cursor/rules)
  • Dependency manifest
  • Reproducible dev env
  • GEMINI.md

What to fix first

  1. 1
    Reproducible dev env
    Add a Makefile or devcontainer or Dockerfile so the agent can set up the project in one command.
    +11.8 pts
  2. 2
    Dependency manifest
    Commit a proper manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) plus a lockfile.
    +9.2 pts
  3. 3
    Linter / formatter config
    Configure a linter/formatter (ESLint+Prettier, Biome, Ruff, rustfmt+clippy, golangci-lint) and commit the config.
    +7.9 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.

GPT-5 Codex
54.1
Kimi CLI
52.8
Claude Code
52.6
Pi
51.1
Devin
50.8
OpenHands
46.8
Gemini CLI
44.7
Cursor
43.5
Aider
38.3

Similar repos

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

All TypeScript repos →

All checks

AGENTS.md / CLAUDE.md· 100% pass
Substantive (1480 chars)
AGENTS.md
.aider.conf.yml· 0% pass
No .aider.conf.yml at repo root
CI configuration· 100% pass
33 GitHub Actions workflow(s)
.github/workflows
CONTRIBUTING guide· 100% pass
Guide present
CONTRIBUTING.md
Cursor rules (.cursor/rules)· 0% pass
No .cursor/rules/*.mdc or .cursorrules
Dependency manifest· 0% pass
No dependency manifest found
Reproducible dev env· 0% pass
No Makefile / devcontainer / Docker / equivalent found
GEMINI.md· 0% pass
No GEMINI.md at repo root
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 (24724 chars)
README.md
Manageable size· 80% pass
1966 files
Test suite· 70% pass
Test files detected (.github/scripts/audit-ci-vuln-scan.test.mjs)
.github/scripts/audit-ci-vuln-scan.test.mjs
Type configuration· 0% pass
No type config found

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/firecrawl/firecrawl
[![Agent Friendly](https://agentfriendlycode.com/api/badge/github/firecrawl/firecrawl.svg)](https://agentfriendlycode.com/repo/github/firecrawl/firecrawl)

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: [main]

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?