Repo brief: bisq-network/bisq

Generated by RepoPilot · document generated 2026-09-12 · concise human review Evidence snapshot · analyzed 2026-09-12T22:38:48.878Z · commit e557bae0d98b

Verdict

Mixed — Single-maintainer risk — review before adopting

• Last commit today
• 3 active contributors
• AGPL-3.0 licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

Bisq is a decentralized peer-to-peer bitcoin exchange that allows users to trade BTC for fiat currencies and altcoins without a central intermediary. It uses multi-signature escrow for transaction settlement, distributed order books, and human arbitration for dispute resolution—enabling non-custodial trading with privacy-first networking. Monorepo structure: core application modules under the root directory (bisq.application plugin via gradle), separate apitest/ subproject for integration testing with own build.gradle, shell/Python scripts for simulation and deployment (apitest/scripts/). Build system heavily customized via bisq.gradle plugin; resources managed through Gradle sourceSets…

Start here

Open these first:

• apitest/src/main/java/bisq/apitest/ApiTestMain.java — Entry point for the API test framework that bootstraps and manages the entire test environment including Bisq instances and…
• apitest/src/main/java/bisq/apitest/Scaffold.java — Core test orchestration class that manages setup, teardown, and coordination of multiple Bisq application instances for…
• apitest/build.gradle — Gradle build configuration that defines dependencies, tasks, and build parameters for the entire API test module.
• apitest/src/main/java/bisq/apitest/config/ApiTestConfig.java — Configuration manager that loads and validates all API test settings, port allocations, and environment parameters.
• apitest/src/main/java/bisq/apitest/linux/BisqProcess.java — Process management wrapper that spawns, monitors, and controls Bisq daemon instances in the test environment.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/bisq-network/bisq.git && cd bisq && ./gradlew clean build && ./gradlew :apitest:installDaoSetup (to fetch dao-setup files required for testing)

Daily commands:

Regular build: ./gradlew clean build. Run API tests (requires DAO setup): ./gradlew :apitest:test -DrunApiTests=true. Simulation scenarios: ./apitest/scripts/trade-simulation.sh, ./apitest/scripts/bsqswap-simulation.sh.…

…shortened for this brief.

Key cautions & unknowns

• Small team — 3 contributors active in recent commits
• Single-maintainer risk — top contributor 93% of recent commits
• AGPL-3.0 is copyleft — check downstream compatibility
• DAO setup files must be downloaded via gradle task (apitest/dao-setup.gradle) before running integration tests—they are not committed to git. Tests are disabled by default (test.enabled = false) and require…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.