us/crw

0

/ 100

Rust206AGPL-3.01d ago
Grade a repo

Polished and well engineered. Punching above its star count.

Fast, lightweight Firecrawl/Tavily alternative in Rust. Web scraper, crawler & search API with MCP server for AI agents. Drop-in Firecrawl-compatible API (/scrape, /crawl, /search). 2.3x faster than Tavily, 1.5x faster than Firecrawl in 1K-URL benchmarks. 6 MB RAM, single binary. Self-host or use managed cloud.

Documentation

94

Contributing guide5pt77

CONTRIBUTING guide found.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under AGPL-3.0.

Engineering

87

Linting and formatting5pt0

No linter or formatter found.

Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.

Reproducibility6pt80

Lockfile present (Cargo.lock). Installs are reproducible.

Tests18pt100

Test files detected (conformance/test_sdk.py).

CI/CD14pt100

CI is configured (.github/workflows/ci.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

79

Dependency manifest6pt55

Dependency manifest found (Cargo.toml).

Housekeeping3pt60

.gitignore present.

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 17
    Forks
  • 55
    Releaseslatest 3mo ago

Community

  • Community health
  • authors own >50% of commits
  • 206
    Watchers

Responsiveness

  • 19h
    Median issue response
  • 1h
    Median PR merge time
  • 0
    Open issues
Repository files48 root entries
  • .claude-plugin
  • .codex-plugin
  • .cursor-plugin
  • .githooks
  • .github
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
    Good: Security policy present.
  • bench
  • blog
  • config
  • conformance
    Good: Test files detected (conformance/test_sdk.py).
  • crates
  • docs
  • examples
  • mcp
  • plans
  • scripts
  • sdks
  • skills
  • tests
  • .dockerignore
  • .DS_Store
    Issue: Build artifacts or local files may be committed (.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • .gitignore
    Good: .gitignore present.
  • .mailmap
  • .mcp.json
  • .release-please-manifest.json
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • COMPATIBILITY-firecrawl.md
  • COMPATIBILITY.md
  • config.default.toml
  • config.docker.toml
  • config.stealth.toml
  • Cross.toml
  • docker-compose.stealth.yml
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • install.sh
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • Makefile
  • package.json
  • 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.
  • README.zh-CN.md
  • release-please-config.json
  • RELEASE.md
  • REVIEW-FIXES.md
  • ROADMAP.md
  • server.json
  • test_api_pipeline.py