swc-project/swcNew scan
88/ 100 · B

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

Rust-based platform for the Web

Rust33,755 starsApache-2.0updated 2d agolarge repo (partial scan)
DocumentationREADME, setup, examples, license
89
EngineeringTests, CI, linting, lockfiles
89
Project healthDescription, activity, stars, deps
86

What to fix first

The highest-impact improvements for this repo.

  1. 1
    CI/CD
    EngineeringInfo

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

  2. 2
    README
    DocumentationInfo

    Show a quick-start snippet so contributors can see what using your project looks like.

  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

89
  • README85
    • This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.
    • README is present.
    • README is well structured with multiple sections.
    • README includes screenshots or visuals. Great for first impressions.
    • README has no code examples (−15 pts).Show a quick-start snippet so contributors can see what using your project looks like.
    • 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 Apache-2.0.
  • Contributing guide86
    • Contributing guide is detailed and thorough.
    • Contributing guide lacks a setup section (−12 pts).Show new contributors how to get a local dev environment running.
    • 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.
    • Optional: add a Code of Conduct (+5 pts).A CODE_OF_CONDUCT.md signals that your project is welcoming. GitHub has a template you can add in one click.

Engineering

89
  • Tests90
    • Test files detected (.github/swc-ecosystem-ci/tests).
    • Rust workspace with test files detected. Run with `cargo test --workspace`.
  • 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.
    • CI runs type checking (tsc, mypy, cargo check, etc.).
    • Optional: report test coverage in CI.Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
    • CI caches dependencies for faster runs.
    • CI tests across multiple environments or versions.
    • CI includes a build step.
  • Linting and formatting60
    • Linter or formatter configured (.github/.prettierrc).
  • Reproducibility70
    • Lockfile present (Cargo.lock). Installs are reproducible.
    • No Dockerfile or runtime version pin found. Adding one earns +10 pts.Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
    • 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

86
  • Dependency manifest100
    • Dependency manifest found (Cargo.toml).
    • Cargo.toml is a workspace manifest for a multi-crate Rust project.
  • Repository metadata70
    • Repository has a description.
    • Primary language detected: Rust.
  • Activity100
    • Actively maintained (pushed within the last month).
    • 33,755 stars.
  • Housekeeping60
    • .gitignore present.
    • Build artifacts or local files may be committed (crates/swc/tests/fixture/jsc-paths/vercel-site/1/input/node_modules/.bin) (−40 pts).Remove them and add to .gitignore.
Repository files39 root entries
  • .agents
  • .cargo
  • .changeset
  • .claude
  • .codex
  • .github
    Good: Test files detected (.github/swc-ecosystem-ci/tests).
    Good: CI is configured (.github/workflows/CI.yml).
    Good: Linter or formatter configured (.github/.prettierrc).
    Good: Issue or PR templates present.
    Good: .gitignore present.
  • .husky
  • .vscode
  • bindings
  • crates
    Warning: Build artifacts or local files may be committed (crates/swc/tests/fixture/jsc-paths/vercel-site/1/input/node_modules/.bin) (−40 pts).Fix: Remove them and add to .gitignore.
  • .gitattributes
  • .gitignore
  • .gitmodules
  • .kodiak.toml
  • .mcp.json
  • .mocha.setup.js
  • .mocharc.js
  • .node-version
  • .npmrc
  • .prettierignore
  • .prettierrc
  • .rustfmt.toml
  • .taplo.toml
  • .tokeignore
  • AGENTS.md
  • ARCHITECTURE.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG-CORE.md
    Good: Contributing guide is detailed and thorough.
    Info: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    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.
  • CHANGELOG.md
  • CLAUDE.md
  • cliff-core.toml
  • cliff.toml
  • clippy.toml
  • CONTRIBUTING.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MAINTENANCE.md
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Info: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.