Dev
Fake GitHub Repository Generator
Demoing a GitHub stats widget, seeding a developer portfolio page, or testing a GitHub API response parser all need realistic repo data — but hitting the real API means tokens, rate limits, and live network calls. This generator produces mock repository records with all the fields a GitHub REST API response contains: repo name, primary language, star count, fork count, open issue count, license, topic tags, creation date, last push date, and a plausible GitHub URL. The language dropdown filters the primaryLanguage field. Choosing JavaScript, Python, Go, Rust, TypeScript, or Ruby locks every generated repo to that language; Any draws from a broader pool including Java, C++, PHP, and Swift. The count input generates between 1 and 20 repos per run. Names follow the adjective-noun pattern common in real open-source projects (awesome-cli, next-hub), and star and fork counts are weighted so most repos have modest numbers with occasional high-star outliers. A practical workflow: generate 10 repos in TypeScript, import the text as a JSON fixture array with light parsing, and feed them to a Storybook repo-card component. Switch to Any language to test how your UI handles different language badge colours or missing fields.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Set the number of repos.
- Choose the primary language.
- Click Generate to produce a result.
- Copy the Generated Repositories and use it where you need it.
Use Cases
- •Seeding a Storybook repo-card component with 10 varied mock repositories across different languages
- •Testing a GitHub API response parser in Jest without burning through rate limits
- •Populating a developer portfolio demo page with realistic-looking starred projects and fork counts
- •Prototyping a GitHub analytics dashboard in Figma with plausible star, fork, and issue numbers
- •Generating sample repo data for a developer-tool tutorial or blog walkthrough on Hashnode or Dev.to
Tips
- →Generate it a few times and keep the version that fits best.
- →Adjust the options above to steer the result toward what you need.
- →Replace the placeholder values with your real data before using it.
- →Everything runs free in your browser — no signup or install required.
FAQ
what fields does a fake github repo include
Each generated repository includes a name, primary language, star and fork counts, open issue count, license type, topics, creation date, and a mock GitHub URL. The shape mirrors a real GitHub REST API response, so you can drop it straight into a parser or UI component.
can I use fake repo data to test a github api integration without hitting rate limits
Yes — the mock data matches the structure of GitHub API responses, letting you test parsers, hooks, and UI components locally without a personal access token or rate-limit concerns. It's especially useful in CI pipelines where live API calls would be unreliable.
how realistic are the generated repository names and stats
Names follow the common adjective-noun pattern used by real open-source projects, so they read as authentic. Star and fork counts are weighted to reflect realistic distributions — most repos have modest numbers, with occasional outliers that look like popular libraries.
is the output JSON that I can parse directly
The output is formatted text, not a JSON object. Each repo is a readable multi-line record with labels like Repo:, Language:, and Stars:. To use it as structured data in a test, you will need to parse the fields, or adapt the raw text into a JSON fixture manually.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.