Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for any developer, agent builder, or team that runs Claude Code, Codex, Cursor, or another coding agent against a long-lived codebase and wants the agent's context discovery to reference a maintained `/openwiki` doc tree instead of re-exploring the codebase every session; install via `npm install -g openwiki` (Node.js 22+, but the action ships Node.js 22 via `actions/setup-node@v4`), run `o
Who should use it
Who should skip it
Move on from langchain-ai/openwiki if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
langchain-ai/openwiki is tracked by RepoRadar as a langchain cli that writes + main in the Documentation & Knowledge section. It was first seen on 2026-07-04 and last updated on 2026-07-04. The current verdict is 'try now' with a Silver tier and easy setup difficulty. langchain-ai/openwiki leads on workflow potential (9.4) and setup ease (8.8); its lowest signal is maturity (6.0), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned langchain-ai/openwiki a composite score of 8.3 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
First-time users should review the auto-append to `AGENTS.md` and/or `CLAUDE.md` after `openwiki --init` — the README explicitly says the CLI "will automatically append prompting to your AGENTS.md and/or CLAUDE.md files" and "If the file does not already exist in your repository, OpenWiki will create it for you"; in workspaces where AGENTS.md / CLAUDE.md are owned by another tool (e.g. a shared corporate policy doc) the user should pre-allocate a tag or section or run OpenWiki against a `--no-agents-md` flag once it ships (not in the public CLI yet as of v0.0.1; the README calls it out as a known limitation); The example Action runs `schedule: - cron: "0 8 * * *"` daily and `openwiki --update --print` writes to the `/openwiki` doc tree and opens a PR — users who want biweekly or weekly cadences should adjust the cron expression; users who don't want auto-PRs should comment out the `peter-evans/create-pull-request` step and run `openwiki --update --print` only as a logged diagnostic; The default model in `examples/openwiki-update.yml` is `z-ai/glm-5.2` (Z.AI / Zhipu GLM 5.2 on OpenRouter) — pick a model with cost-control in mind; large repos with many commits between cron runs can rack up significant inference cost under `GLM 5.2` / `Kimi K2.6` / `Sonnet 5`; users who want lower-cost cron runs should set `OPENWIKI_MODEL_ID` to a smaller model (e.g. `anthropic/claude-haiku-4.5` on OpenRouter); `LocalShellBackend` lets the agent run shell commands against the user's repo during doc generation — the same risk surface as any coding-agent with shell access; users in shared / corporate / regulated environments should review the doc-gen PR carefully for unexpected shell side effects (e.g. an unintended `git config` change, an unintended file write outside `/openwiki` — the `--update --print` Action scope is `add-paths: openwiki` so the PR can only edit `/openwiki`, but the LocalShellBackend itself runs against the user's repo during doc generation).