Code checks for JavaScript and TypeScript

AI accelerates development. Swarm enforces your standards.

Swarm checks the changes you’re about to commit for code quality and security problems. Use the same checks in your automated builds, with rules your team chooses.

Install Swarm See what it checks

$ npm install --save-dev zedbee
$ npx zedbee init

Illustrative scan · staged diff · one command

zsh — zedbee

~/Projects/TrillionDollarIdea/npx zedbee scan

Checks (2.5s)

Formattingfail
Lint1.8s
TypeScript1.8s
Cyclomatic complexity1.8s
Readability complexity1.8s
Structural security1.8s
Secrets1.8s
React correctness1.8s
React accessibility1.8s

Activity

Cyclomatic complexity: checking…

Readability complexity: checking…

Structural security: checking…

Formatting: 1 blocking finding

Cyclomatic complexity: passed

Readability complexity: passed

Summary

Check the code you're about to commit.

Swarm checks the version you staged for commit, including partially staged files. Later edits in your editor don't change the scan.

01 / Your next commit

HEADa41f9c2

STAGED→ Swarm

TREEignored

It checks the commit you are actually making

Swarm checks the changes you selected for commit. Edits you haven’t selected yet stay out of the scan.

02 / What changed

Before

Staged

New problems get stopped. Old debt stays out of the way.

Swarm can look across the project to understand a problem, then checks whether your changes introduced it or made it worse. Existing problems don’t have to stop unrelated work.

fmtlinttypescomplexitysecuritysecretsdupesdepsdead codereacta11yvulns

Your code checks, together.

Twelve categories of checks, managed together and invoked with one command.

.zedbeerc.jsoncvs

~~.eslintrc.cjs.prettierrctsconfig.lint.json~~

Configure your checks in one place.

Swarm manages the versions and settings of the tools it runs. You choose your team's rules in one configuration file instead of setting up each tool separately.

terminaljsonsarif 2.1.0

For developers, builds, and agents

Read results in your terminal, or pass them to your build system and coding agents. The formats differ; the decision stays the same.

Pass0

Blocked1

Incompl.2

Know when a check couldn’t finish.

If a required check cannot finish, Swarm says so. You can tell the difference between “no problems found” and “the check didn’t run.”

New problems should block the commit. Old problems should not block the team.

Before the commit

Catch problems before you commit.

Swarm checks your changes before they become a commit and reports the problems those changes introduce or make worse. You can fix them while the work is still fresh, before a teammate reviews the code or CI runs.

01Editor
02git add
zedbee scanblocks only new or worse
04Commit
05Code review

Checks in one place

Your code checks, managed together.

Swarm brings checks for formatting, type errors, security issues, and more into one tool. You can see which checks are enabled, which files they cover, which tools run them, and what they can and cannot catch.

$ npx zedbee checks

Formattingprettier · pinned

Linteslint · managed rules

Typestsc · project-wide

Complexitycyclomatic · readability

Zedbee Swarmone policy · one contract

Securitystructural · secrets

Duplicationtoken-level

Dependenciesarchitecture · vulns

React · a11ycorrectness · dead code

A careful approach

Check your code without running scripts from your project.

Swarm checks a separate copy of your code. It uses its own settings instead of running configuration scripts from your project. It verifies downloaded tools, checks staged files for exposed secrets, such as passwords and API keys, and tells you when a check needs network access.

Trust boundary

isolated snapshot: read-only
managed rules: inert
execution: shell-free
binaries: checksum-verified
secrets: redacted
network: disclosed

← untrusted reporesult →

Fixes stay reviewable

zedbee fix previews supported fixes, requests approval, and writes only to working files. It never stages or commits on the developer’s behalf.

01 Preview

- const x = foo( a,b )
+ const x = foo(a, b);

02 Approve

Apply 1 fix to src/util.ts?
[y]es / [n]o / [d]iff

03 Apply
```
wrote src/util.ts
index unchanged
```
04 Review & stage
```
$ git diff
$ git add src/util.ts
```

The same checks for developers, builds, and AI agents.

Swarm uses the same rules whether you run it yourself, include it in an automated build, or have an AI agent run it. You get readable results in your terminal. Build systems and agents get structured results that show what went wrong, where it happened, and how to fix it.

Developer terminal

✗ Formatting fail✓ Lint 1.8s✓ Complexity 1.7s

The decision

BLOCKED 1

ZB-FMT-0012 · src/billing/usage.ts:42
introduced in staged change

{
  "outcome": "blocked",
  "exitCode": 1,
  "checks": [
    {
      "checkId": "formatting",
      "status": "completed",
      "durationMs": 18,
      "findings": [
        {
          "id": "ZB-FMT-0012",
          "check": "formatting",
          "rule": "prettier",
          "severity": "error",
          "message": "Staged code does not match the managed format.",
          "location": {
            "file": "src/billing/usage.ts",
            "startLine": 42,
            "endLine": 42
          },
          "remediation": "Format the staged lines, then stage the result.",
          "automaticFix": {
            "available": true,
            "command": [
              "npx",
              "--no-install",
              "zedbee",
              "fix",
              "formatting"
            ],
            "scope": "working-file",
            "writes": "working-tree",
            "stagesChanges": false
          },
          "attribution": {
            "kind": "transformation-diff",
            "staged": true,
            "evidence": [
              "Prettier transformation overlaps staged target lines 42-42"
            ]
          }
        }
      ]
    }
  ]
}

Coding agent

id: ZB-FMT-0012
loc: usage.ts:42
fix: available
attribution: staged

AI can write the code. Your team still owns the standard.

Put a dependable gate in front of the next commit.

Set up Swarm with a guided preview. See which rules it recommends, when it needs an internet connection, and which project files it will change before you apply anything.

$ npm install --save-dev zedbee
$ npx zedbee init

Install Swarm Explore the check suite

staged

commit