forgedock weekly downloads statistics

<div align="center"> <img src="https://avatars.githubusercontent.com/in/4051319?s=200&v=4" alt="ForgeDock" width="80" /> <h1>ForgeDock</h1> <p><strong>From GitHub issues to reviewed, tested, merged changes, autonomously.</strong></p> <p>ForgeDock runs AI coding agents through validation, implementation, review, CI and merge, one issue per lane, many lanes in parallel. Every step is recorded on GitHub, so runs survive crashes, later agents build on earlier ones, and you can audit everything.</p>

<a href="LICENSE"><img src="https://img.shields.io/badge/License-AGPL--3.0-blue.svg" alt="License: AGPL-3.0" /></a> <a href="https://www.npmjs.com/package/forgedock"><img src="https://img.shields.io/npm/v/forgedock?color=cb3837&logo=npm" alt="npm" /></a> <a href="https://docs.anthropic.com/en/docs/claude-code"><img src="https://img.shields.io/badge/Built%20for-Claude%20Code-blueviolet" alt="Claude Code" /></a> <a href="https://github.com/RapierCraftStudios/ForgeDock/stargazers"><img src="https://img.shields.io/github/stars/RapierCraftStudios/ForgeDock?style=social" alt="GitHub Stars" /></a>

<p>📖 <a href="https://rapiercraftstudios.github.io/ForgeDock/">Documentation</a> · <a href="#try-it-in-30-seconds">Try it</a> · <a href="#the-evidence">Evidence</a> · <a href="#what-works-today">What works today</a></p> </div> <div align="center"> <img src="docs/demo.gif" alt="ForgeDock running several GitHub issues in parallel: lanes validate, build, review and merge, flipping workflow labels live" width="900" /> </div>

What it does

You file issues. ForgeDock turns each one into a merged pull request:

issue → validate → plan (frozen contract) → implement → review → PR → CI → merge

• One lane per issue, many in parallel. forgedock orchestrate schedules a batch from the issues' Depends on #N lines, runs up to K lanes at once, and recovers the mechanical failures itself (CI red, merge conflicts, engine errors). It asks you only about product, spend, credentials and releases.
• Durable. Each lane records its state on the issue and in a crash-safe run log. Kill it, restart it, or lose the session: it resumes from what GitHub says, and two lanes never own the same issue.
• Checked, not trusted. Each change is held to a contract frozen before implementation. It must pass a separate review (which blocks on unimplemented requirements and regressions) and CI. On paths you mark as risky, the full contract-conformance gate also blocks. Before anything reaches your default branch, a staging review with a panel of domain reviewers (security, concurrency, auth, CLI, regression risk…) must post a gate marker.
• GitHub is the memory. Findings, decisions and trajectories are written as structured comments that later lanes read. Nothing lives only in a chat window.

ForgeDock orchestrates delivery. It does not replace the model: it runs on your Claude Code account and resells no compute.

Try it in 30 seconds

Needs: Claude Code (subscription or ANTHROPIC_API_KEY) · GitHub CLI (authenticated) · Node.js ≥ 18.

npx forgedock demo     # creates a throwaway repo and runs the pipeline end to end

To use it on your own repo:

npm install -g forgedock      # the CLI and the durable engine
forgedock                     # checks your environment, installs the commands, writes a forge.yaml for you to review
forgedock run-issue 42        # one issue, start to merge
forgedock orchestrate 41 42 43 --parallel 3    # a batch, scheduled from its Depends-on lines

Inside Claude Code the same flows are /work-on 42 and /orchestrate. All install options (plugin marketplace, OpenCode, headless/CI) are in Install.

The evidence

ForgeDock is built with ForgeDock. Every number below is from this repository's public history and you can recount it.

Last 30 days (2026-09-24 → 2026-10-23)
Issues filed / closed	800 / 784
Pull requests merged	613
Issues that are the pipeline's own review findings	396 (about half)
Issue opened → merged and closed, median	2 h 19 min (p25 55 min, p75 10 h; 475 issues)
Since 2026-06-04: PRs merged / releases	1,961 / 85

gh api -X GET search/issues -f q="repo:RapierCraftStudios/ForgeDock is:pr is:merged merged:2026-09-24..2026-10-23" --jq .total_count

Runs you can open and read end to end:

• #1230: the staging review found dead code in a feature shipped three hours earlier, then review caught a bug in the fix itself. 30 minutes from issue to merge.
• #1172: review found an ANTHROPIC_API_KEY exfiltration path in the headless runner; fixed in 18 minutes with regression tests. A later review found a bypass of that fix (#1243).
• #952: the pipeline closed its own proposal as invalid, with receipts: the work had shipped weeks earlier. No code written.
• #4442: a large feature split into six dependent sub-issues (#4448–#4453) that the batch runner built in dependency order.

What the gates caught

The staging review runs before every release. The releases of 2026-10-22 and 2026-10-23 alone stopped these defects before they shipped. Each was found by a reviewer, filed, fixed by a lane and re-verified:…