getsentry/responses

A utility for mocking out the Python Requests library.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 35 minutes ago
Added to GitGenius on September 16th, 2026
Created on November 15th, 2013
Open Issues & Pull Requests: 42 (+0)
GitHub issues: Enabled
Number of forks: 380
Total Stargazers: 4,343 (+0)
Total Subscribers: 91 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.8 hours
Mean response time: 61.2 days
90th percentile: 214.3 days
Tracked items: 28

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 15
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 496 days
Stale 30+ days: 14
Stale 90+ days: 14

Recent activity

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

Top labels

  • bug (9)
  • enhancement (9)
  • Waiting for: Product Owner (6)
  • question (3)
  • Improvement (2)
  • Feature (1)
  • Stale (1)

Most active issues this week

Detailed Description

responses is a library for mocking the Python Requests library in tests.

The library solves the problem of testing code that makes HTTP requests without hitting real endpoints. It works by intercepting calls to the Requests library and returning predefined responses, allowing developers to test request handling logic in isolation. This approach avoids network dependencies, speeds up test execution, and enables testing of error conditions and edge cases that would be difficult to trigger against real services.

Developers should choose this tool when writing unit or integration tests for applications that depend on HTTP requests through the Requests library. It suits projects where you need deterministic test behavior without external service availability, and where you want to verify that your code correctly handles various HTTP responses and error scenarios. The library is particularly valuable for testing error handling paths and ensuring your application behaves correctly when remote services return unexpected responses.

The project maintains a steady cadence of releases with regular updates addressing bug fixes and feature requests. Pull requests receive timely review and feedback from maintainers. The codebase shows active maintenance with issues being addressed and closed regularly. Development activity demonstrates consistent engagement with the community through responsiveness to reported problems and contributions.