Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for technically capable bioinformatics users and life-science builders who want an open, local-first starting point for genome interpretation workflows instead of shipping raw data straight into a black-box consumer app.
Who should use it
Who should skip it
Avoid running exon-research/genomi in production until you have reviewed its permissions, data-access scope, and failure modes in a sandbox.
About this signal
exon-research/genomi is tracked by RepoRadar as a ai product in the Science Tools section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'worth watch' with a Silver tier and hard setup difficulty. exon-research/genomi leads on open-source/build quality (8.4) and workflow potential (8.2); its lowest signal is setup ease (4.2), 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 exon-research/genomi a composite score of 7.8 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 'medium' 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 read AI benchmarks without getting fooled for the checklist behind this score.
Risk explanation
It works with genomic files and can generate health-related interpretations, so testing should stay on consented non-production datasets under the same privacy controls as the source data; Local-first handling reduces data movement, but any health or trait conclusion still needs clinician or domain-expert review before it informs a real decision.