What your code says about your components
Usage analytics for design-system teams, built for React and Vue. Open source and self-hosted, so nothing leaves your infrastructure.
Repos
partner-portal
Button@acme/ui·4.2.038 uses (+9)·17 files@acme/ui4.2.01738 (+9)TabsAdded@acme/ui·4.2.03 uses (+3)·2 files@acme/ui4.2.023 (+3)Dialog@acme/ui·4.2.09 uses (+2)·7 files@acme/ui4.2.079 (+2)Modal@acme/legacy-ui·2.14.05 uses (−2)·4 files@acme/legacy-ui2.14.045 (−2)TabBarRemoved@partner-portal/shared0 uses (−3)@partner-portal/shared——0 (−3)Button@acme/legacy-ui·2.14.024 uses (−8)·11 files@acme/legacy-ui2.14.01124 (−8)partner-portal
ButtonExternalReact
@acme/ui·v4.2.0
Usage38Composition
Adoption
Chart the adoption of any component
Any mix of libraries, packages or components, across all your repos or just one, scan by scan.
Core componentsAll repos
Button@acme/uiDialog@acme/uiTabs@acme/ui
ButtonDialogTabsUsage
See which props and values teams actually pass
Every use, with the values it passes, linked to its line of code.
partner-portalButton@acme/ui
Prop values
variant32
primary17secondary9danger(selected)3ghost3
Uses· variant=danger2 files · 3 uses
src/orders/OrderTable.tsx2 uses:88variant=danger:112variant=danger
src/components/ConfirmDialog.tsx1 use:34variant=danger
Impact
See everything that depends on a component
Every component that renders it, directly or further up, so you know which screens a change will reach.
partner-portalButton@acme/ui
Migration
Mark what's replacing what, and watch the move
Mark a whole package or a single component as replaced, and every scan shows how much has moved to its replacement.
Migrations · 2 in progress
@acme/legacy-uito@acme/ui73.6% migratedup from 69.8% previouslyButton · @acme/legacy-uitoButton · @acme/ui60.9% migratedup from 57.9% previouslyRetirement
See who still uses what you're retiring
Retired components show the uses that remain, and where.
Retirements · 1 in progress
Carousel · @acme/legacy-ui31 left in 2 reposdown from 40 previouslySelf-hosted
Run it on your own infrastructure
- One Docker image or a Helm chart, and a Postgres database
- Your own sign-in, through any OIDC provider
- Scans uploaded from CI or a laptop
- Open source, MIT licensed