Open Source DeepWiki: AI-Powered Wiki Generator for GitHub/Gitlab/Bitbucket Repositories. Join the discord: https://discord.gg/gMwThUMeme
17.2k
Stars
1.9k
Forks
264
Open issues
30
Contributors
AI Analysis
DeepWiki is an AI-powered wiki generator that automatically creates comprehensive documentation and interactive wikis for GitHub, GitLab, and Bitbucket repositories by analyzing code structure, generating docs, and creating visual diagrams. It is specialized for developers and repository maintainers who want to rapidly generate professional documentation without manual writing, and is less relevant for users who need custom documentation beyond automated analysis.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Open-source tool auto-generates interactive wikis from any Git repository using AI
DeepWiki-Open analyzes GitHub, GitLab, and Bitbucket repositories to automatically produce structured documentation, visual diagrams, and navigable wikis. It targets developers, engineering teams, and open source maintainers who need to quickly understand or document unfamiliar codebases. With 17K stars accumulated within roughly 13 months of creation, it has captured meaningful developer attention. Its core value proposition is reducing the friction of documentation from scratch by using AI to infer structure and generate explanations directly from source code.
Created in late April 2025 as an open-source reimplementation of the commercial DeepWiki product. A v2.0 update branded 'Grok Wiki' was later released, adding a hosted version at grok-wiki.com, suggesting the project evolved from pure OSS toward a hybrid OSS/SaaS model.
Rapid early viral growth typical of AI-powered developer tooling released in 2025, likely driven by social sharing on Twitter/X and Discord. The multilingual README (10 languages) signals an intentional effort to reach a global audience. Growth has since stabilized — 83 stars in the last 7 days as of June 2026 is modest but not negligible for a 13-month-old repo, indicating a sustained long tail rather than pure flash-in-the-pan attention.
A hosted deployment at grok-wiki.com exists, indicating at least some real-world usage. Discord server presence implies an active user community. Forks (1,918) suggest developers are building on or customizing it. However, no documented case studies, usage metrics, or enterprise adoption data are available in the README. Adoption appears real but scale is unverified beyond GitHub signals.
Likely a web application with a Python backend that orchestrates LLM API calls for code analysis and documentation generation, combined with a frontend for wiki display. The README references visual diagrams, suggesting either Mermaid or similar diagram-as-code rendering. Multi-platform support (GitHub/GitLab/Bitbucket) implies an abstracted repository fetching layer. Architecture details beyond this are not confirmed in the available README excerpt.
Not documented in README
Last push was June 3, 2026, approximately 22 days before the evaluation date — indicating active maintenance. The project is under 14 months old and has received a major v2.0 update, suggesting ongoing development rather than abandonment. Discord community presence provides a feedback channel. The README is sparse in this excerpt, which limits confidence in assessing depth of maintenance.
ADOPT IF: you need to quickly generate baseline documentation or onboarding wikis for existing codebases and are comfortable reviewing AI-generated output for accuracy. AVOID IF: you require production-grade, curated documentation with guaranteed accuracy or need enterprise support and SLA guarantees. MONITOR IF: you're evaluating AI documentation tooling for team adoption — the project is active but long-term maintenance commitment and output quality at scale remain insufficiently documented.
Independent dimensions
Mainstream potential
4/10
Technical importance
6/10
Adoption evidence
3/10
- AI-generated documentation can be inaccurate or miss critical nuances — human review overhead may offset the automation benefit for complex codebases.
- The project is less than 14 months old with a sparse public README; long-term maintenance commitment is unproven, and the solo-maintainer or small-team risk is real.
- The hybrid OSS/SaaS model (grok-wiki.com) creates uncertainty about which features remain open source over time and whether the hosted service could diverge from the self-hosted version.
- Dependency on third-party LLM APIs means output quality and cost are tied to external providers; API pricing changes or deprecations could materially affect usability.
- Competitive pressure from better-resourced players (e.g., PandaWiki, commercial tools) and from LLM providers building similar features natively could limit the project's differentiated value over time.
Likely to maintain a stable niche as a self-hostable, multi-platform wiki generator. The SaaS pivot suggests a path toward sustainability, but mainstream dominance appears unlikely given well-resourced competitors. Continued incremental growth is probable.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://grok-wiki.com/
- Language
- Python
- License
- MIT
- Last updated
- 1mo ago
- Created
- 15mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
uv.lock pins requests 2.32.3, below the 2.32.4 fix for CVE-2024-47081
Security: multiple requests advisories appear reachable in deepwiki-open
Unauthenticated arbitrary server file read (source/config/JSON/YAML) and git-clone SSRF via the repo_url parameter on the all-interfaces, CORS-wildcard DeepWiki API
Repository file fetch follows redirects with environment netrc auth enabled
Private security disclosure contact requested
Top contributors
Recent releases
No releases published yet.
Similar repos
AIDotNet/OpenDeepWiki
OpenDeepWiki is a self-hosted knowledge management platform that transforms Git...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
AsyncFuncAI/deepwiki-open
this
|
17.2k | +88 | Python | 6/10 | 1mo ago |
|
AIDotNet/OpenDeepWiki
|
3.4k | — | C# | 7/10 | 3d ago |
 langchain-ai/openwiki
|
10.2k | — | TypeScript | 7/10 | 7h ago |
 FSoft-AI4Code/CodeWiki
|
1.3k | — | Python | 7/10 | 6d ago |
 sopaco/deepwiki-rs
|
1.3k | — | Rust | 7/10 | 2mo ago |
 SamurAIGPT/llm-wiki-agent
|
3.2k | — | Python | 7/10 | 6h ago |
PandaWiki (9,833 stars) is the closest direct competitor in the AI-wiki generation space, with significantly more stars and likely more mature production usage. DeepWiki-Open differentiates by supporting multiple Git platforms and emphasizing code-level diagram generation, but PandaWiki has a meaningful head start in adoption evidence.
Shares the LLM-powered wiki generation concept with 3,017 stars. Appears to be an earlier, less feature-rich approach. DeepWiki-Open's multi-platform support and v2.0 hosted offering likely position it as the more actively developed option.
Commercial documentation platforms that require manual authoring but offer polish, team features, and reliability. DeepWiki-Open trades manual control for automation speed. Teams needing production-grade, curated docs will likely still prefer commercial tools.
Targets Obsidian users specifically, a narrower niche. DeepWiki-Open is more broadly applicable to any repository consumer regardless of note-taking toolchain.
These tools answer questions about code inline rather than generating persistent wiki artifacts. DeepWiki-Open produces a standalone navigable output, filling a different workflow slot — artifact generation vs. interactive Q&A.
