httpcats/http.cat

:cat: HTTP Cats API

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 3 minutes ago
Type:Server / PlatformCategory(s):API Development ToolsDeveloper Tools
Added to GitGenius on September 18th, 2026
Created on August 30th, 2015
Open Issues & Pull Requests: 38 (+0)
GitHub issues: Enabled
Number of forks: 208
Total Stargazers: 3,701 (+0)
Total Subscribers: 26 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 42.4 hours
Mean response time: 152.4 days
90th percentile: 674.4 days
Tracked items: 8

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,033 days
Stale 30+ days: 8
Stale 90+ days: 8

Recent activity

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

Top labels

  • bug (1)
  • feature (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

http.cat is an API that serves cat images corresponding to HTTP status codes.

The project solves the problem of making HTTP status codes memorable and shareable by pairing each code with a relevant cat image. The API is implemented through Nginx server configuration rather than server-side code, making it lightweight and efficient. Users can request a status code via URL and receive the corresponding cat image, with optional JSON responses available.

The tool suits anyone building documentation, error pages, or educational content around HTTP status codes who wants to add visual humor and engagement. It works well for developers creating status code references or testing tools. The project welcomes contributions to expand coverage of HTTP status codes, providing templates and clear documentation for adding new images and status descriptions in multiple languages including Catalan.

The project maintains an active development cycle with regular updates to its technology stack, having migrated from React with pre-rendering to Next.js for its current version. The codebase is organized with clear separation between image assets, status code metadata, and content documentation, making contributions straightforward for new maintainers. The project accepts pull requests for new status code coverage and actively manages the addition of images and multilingual content descriptions.