Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams building document-heavy AI workflows that need one serious extraction layer instead of a pile of single-format parsers and ad hoc OCR scripts.
Who should use it
Who should skip it
Consider kreuzberg-dev/kreuzberg lower priority if you already have a working solution in this category.
About this signal
kreuzberg-dev/kreuzberg is tracked by RepoRadar as a framework in the Radar section. It was first seen on 2026-06-19 and last updated on 2026-06-19. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for kreuzberg-dev/kreuzberg are workflow potential (10.0) and practical usefulness (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed. 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 kreuzberg-dev/kreuzberg a composite score of 8.9 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 82.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 project can ingest private documents and optionally connect to hosted OCR or LLM providers, so verify both the data path and the Elastic License 2.0 usage terms before adopting it in a commercial workflow.