Skip to main content
Back to Dev generators

Dev

Fake GitHub Repository Generator

Used by developers, writers, and creators worldwide.

A fake GitHub repository generator creates realistic mock repo metadata for populating developer portfolio demos, testing GitHub API integrations, and building dashboard prototypes. Every generated repo includes a name, primary language, star and fork counts, open issues, license, topics, creation date, and a plausible GitHub URL — exactly the fields you'd see in a real API response. Choose from JavaScript, Python, Go, Rust, TypeScript, or Ruby as the primary language, and generate up to any count you need in one click. This makes it easy to seed a Storybook component with varied repo cards or stress-test a GitHub stats widget without hitting rate limits or needing a personal access token.

Loading usage…

Free forever — no account required

How to use

  1. Choose your options above
  2. Click Generate
  3. Copy your result

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

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.