Developers

API and feeds

Read the OSS Graveyard catalogue programmatically: a free, read-only JSON API and Atom feeds.

The catalogue is public. The API is read-only, needs no key, allows cross-origin requests (CORS) and only returns published (moderator-approved) data. Please cache responses and keep to a few requests per second; responses already carry Cache-Control headers.

Versioning

All endpoints live under /api/v1 and send an X-API-Version: 1 header. Within v1, fields may be added but are never removed or renamed. Breaking changes would ship as /api/v2, with v1 kept running for at least six months. The older unversioned /api/projects still works and points to its successor in a Link header.

Search projects

GET /api/v1/projects

Parameter	Values
`q`	Free-text search (name, description, tags)
`status` (repeatable)	abandoned, dormant, seeking_revival, revival_in_progress, revived, forked, revival_failed
`work` (repeatable)	maintenance, bug_fixing, dependency_updates, security, porting, modernization, documentation, testing, build_ci, performance, accessibility, localization, ui_ux, feature_completion, reimplementation, rewrite, fork, successor, community_building, infrastructure, other
`type` (repeatable)	application, library, framework, cli, desktop_app, mobile_app, web_app, browser_extension, game, game_engine, plugin, developer_tool, server, self_hosted_service, operating_system, hardware_firmware, dataset, api, bot, automation_tool, educational, documentation_resource, theme, package_distribution, other
`effort` (repeatable)	tiny, small, medium, large, huge, unknown
`skill` (repeatable)	beginner, intermediate, advanced, expert
`language`, `tech`	Exact language or technology tag
`sort`	relevance, recent, name, stars, revivals, stale
`page`	1-based page number (24 per page)

curl 'https://ossgraveyard.dev/api/v1/projects?status=seeking_revival&effort=small&sort=stars'

{
  "total": 12, "page": 1, "pageCount": 1,
  "items": [{ "slug": "...", "name": "...", "status": "seeking_revival",
              "revivalCount": 0, "repository": { "stars": 1234, ... },
              "url": "https://ossgraveyard.dev/projects/..." }]
}

One project

GET /api/v1/projects/{slug} returns the full entry, including revivals (each with type: fork, rewrite, reimplementation, successor, alternative, compatibility_layer, replacement, other), repository metadata with its fetchedAt time, and lastVerifiedAt. Unknown or unpublished projects return 404.

Discussion

GET /api/v1/projects/{slug}/discussion returns the public threads and replies (author display name, handle and ranks; never user ids or emails). Comment bodies are plain text in the site's small comment syntax.

Atom feeds

/feeds/projects.xml: new projects
/feeds/revivals.xml: new revival efforts
/feeds/updates.xml: “revival update” posts by verified maintainers and moderators
/projects/{slug}/feed.xml: revivals and updates for one project (also linked from each project page)

Preview images

/og/projects/{slug}.png is a 1200×630 card for each published project, used for social previews. Feel free to embed it with a link back.

Terms

Catalogue text is contributed by the community under the terms of service; please attribute OSS Graveyard and link to the project page when you republish entries. Repository statistics come from GitHub, GitLab and Codeberg and are evidence, not verdicts (see the methodology). Report problems or request higher limits through contact.