Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Most AI researchers + RAG engineers + knowledge-management power users today have built knowledge-graph extraction workflows that require stitching together a hand-wired extraction prompt (per-LLM provider credential handling + custom chat-template handling + per-provider cost telemetry) + a hand-built entity normalization layer (hand-written canonicalization rules that break every time a new doma
Who should use it
Who should skip it
Skip hanxiao/knowledge-graph-extractor if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
hanxiao/knowledge-graph-extractor is tracked by RepoRadar as a tool in the Radar section. It was first seen on 2026-07-09 and last updated on 2026-07-09. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, hanxiao/knowledge-graph-extractor is strongest on momentum (9.0) and workflow potential (8.9) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. 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 hanxiao/knowledge-graph-extractor a composite score of 8.2 out of 10, placing it in the Gold 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 0.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
The 211* repo is at solid active maintenance (created 2026-04-15; MIT verified on 2026-07-09) but the consumer SHOULD note that the project requires a single NVIDIA L4 24GB GPU (e.g. GCP g2-standard-8) + Docker + NVIDIA Container Toolkit + 17GB of GGUF model storage in `models/`; the optional JINA_API_KEY (from https://jina.ai/api-key; has a free tier.