dreamhead/moco

Easy Setup Stub Server

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 48 minutes ago
Added to GitGenius on September 15th, 2026
Created on October 18th, 2012
Open Issues & Pull Requests: 147 (+0)
GitHub issues: Enabled
Number of forks: 1,080
Total Stargazers: 4,443 (+0)
Total Subscribers: 268 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 40.4 hours
Mean response time: 353.8 days
90th percentile: 705.9 days
Tracked items: 2

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 537 days
Stale 30+ days: 4
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Moco is a stub server framework that simplifies setting up mock HTTP endpoints for testing and development.

The tool addresses the friction of integration testing against external services by providing a lightweight alternative to deploying full application servers. Rather than building and redeploying WAR files to test different service responses, developers define stub behavior in configuration files and run Moco as a standalone server. The framework accepts JSON configuration describing request matching rules and corresponding responses, then serves those responses when requests arrive.

Moco suits projects that need to mock HTTP-based integrations during development and testing, particularly REST APIs and web services. It works both as a standalone runner launched from the command line and as an embedded library within Java applications. The tool supports HTTP, WebSocket, and Server-Sent Events protocols. Developers can extend Moco's built-in matching and response capabilities through custom implementations when the standard API does not meet their requirements.

The project maintains active build automation and accepts community contributions. Documentation covers HTTP APIs, REST endpoints, WebSocket support, SSE functionality, global settings across multiple configuration files, command-line usage, and extension mechanisms. The codebase requires Java 17 or later and uses Gradle for building.