Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for any student, researcher, or self-learner who works with textbook-grade PDFs or Markdown files and wants a measurable mastery surface — concept visualizations on demand, a four-axis per-concept mastery score that updates after every study session, and a bring-your-own-AI workflow that reuses an existing ChatGPT / Claude / Gemini subscription without a second bill. The PDF/Markdown-taggin
Who should use it
Who should skip it
Pass on beltromatti/get-it if its scope or audience does not match what your team is building right now.
About this signal
beltromatti/get-it is tracked by RepoRadar as a pdf/markdown study companion wit in the Learning & Education section. It was first seen on 2026-07-04 and last updated on 2026-07-04. The current verdict is 'try now' with a Gold tier and easy setup difficulty. beltromatti/get-it leads on workflow potential (9.2) and practical usefulness (9.0); its lowest signal is maturity (6.4), 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 beltromatti/get-it a composite score of 8.1 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 1.0 and never affects the composite score or tier. The risk label of 'low' 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 README badge says 'License — MIT' but the raw LICENSE file in the repo is 'License — Apache 2.0, January 2004' — the cycle 147 README-license-badge-display-bug pattern: the raw LICENSE is canonical (Apache-2.0 here); the badge is a known display artifact and should be fixed in a docs pass so future agents don't try to 'correct' the LICENSE backward; Windows builds are intentionally unsigned — Microsoft Trusted Signing requires a paid Azure subscription the project doesn't carry, so the first launch shows a SmartScreen warning 'Windows protected your PC' — explicit 'More info → Run anyway' guidance is in the README, but in multi-user / regulated / compliance-monitored environments, unsigned binaries may be quarantined before the user can override; Bring-your-own AI means the user owns the API costs and rate limits — the app surfaces rate-limit countdowns but does not retry in a loop, so large study sessions on free tiers will hit provider rate limits and the app stops cleanly; the README documents this transparently but a user expecting indefinite AI access on a free tier may hit the wall; The page tagger agent's inline concept tags are placed by an LLM call against the document text — on long PDFs the tagger may take a while on the first pass; on documents where the tagger crashes the self-repair 'repairing' message replaces red text but the user should expect to wait a few minutes for the first pass on a 500-page PDF.