Repositories read with their docs
Intended use comes from the documentation a project publishes, not a guess from a function signature.
Web index · sourcing
Web data for technology teams
Repositories findable by what they do, read with their documentation attached, alongside the discussion threads that resolved the same error you're looking at.
What's actually in it
The documents this work actually runs on.
Threads that actually resolved something
The accepted answer in a Q&A thread leads, rather than the longest reply.
Licence carried with the code
Held alongside the repository, because it decides whether you can use it at all.
Hiring signal read from the posting
Roles read from the employer's own careers page, not an aggregator's altered copy.
Built on this index
The workspaces this data feeds.
Status is shown per workspace — a “soon” workspace is on the roadmap, not available today.
The collections behind it
Browse the shelves this page draws from.
Questions
Frequently asked.
- Does it distinguish a maintained repo from an abandoned one?
- Activity and licence are read as structured fields alongside the repository, so that question doesn't require opening the project yourself.
- Which workspaces read this today?
- Code and Projects are live; Workflow is in beta and reads the same material as it ships.
Web data for technology teams
Put the index to work.
Request private access and we'll walk through the collections and workspaces above.
Browse the rest of the catalog at /apps.
Request access