Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers and teams that need structured extraction from sensitive documents without sending the raw files to a hosted AI API.
Who should use it
Who should skip it
Skip parsehawk/parsehawk if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
parsehawk/parsehawk is tracked by RepoRadar as a developer tool in the Document AI section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, parsehawk/parsehawk is strongest on workflow potential (9.4) and open-source/build quality (8.4) and weakest on momentum (4.0) — 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 parsehawk/parsehawk a composite score of 8.3 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 3.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
It is built for sensitive documents, so you still need to validate local storage, logs, and model placement before running real customer or regulated files through it; The default practical path depends on local model runtime setup and enough Apple Silicon memory or NVIDIA VRAM for the verified workflow; Windows is not supported yet, which narrows the easiest early-adopter path to macOS Apple Silicon or Linux NVIDIA setups.