Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for designers and frontend builders who want to capture a live product's design system as structured AI-ready guidance instead of rebuilding the same visual tokens by hand.
Who should use it
Who should skip it
Skip bergside/design-md-chrome if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
bergside/design-md-chrome is tracked by RepoRadar as a design extraction extension in the Developer Tools section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'try now' with a Gold tier and easy setup difficulty. Across RepoRadar's eight signals, bergside/design-md-chrome is strongest on workflow potential (9.9) and practical usefulness (9.0) and weakest on maturity (6.7) — 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 bergside/design-md-chrome a composite score of 8.4 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 6.0 and never affects the composite score or tier. The risk label of 'none' 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
No inherent user-impacting risk is flagged from the captured evidence.