shadcn.io is not affiliated with official shadcn/ui
License Compliance Dashboard Block for Solid
A licence policy of four families as checkboxes, twelve packages split live into Compliant and Needs review with counts and a score, and a line explaining why a pressed package sits where it does.
Installation
Overview
Check your dependencies against a licence policy with this compliance panel for Solid with Ark UI. A hairline frame with a plus mark on each corner holds a rail of four licence families, permissive, weak copyleft, strong copyleft and unknown or custom, each a Checkbox for allowed or not with the licences it covers written out. Beside it, twelve invented Permitfold packages sit in two tables, Compliant and Needs review, with a count on each and a score. Ticking a family moves its packages between the tables in place, so the page keeps its height, and a polite line says what changed. Pressing a package reads why it sits where it does, in a sentence that names its licence and what that family asks of you. It's built from Checkbox, Field, Badge and Guides. Not legal advice. For open-source programs, procurement reviews and release checks.
FAQ
How do I use my own packages and families?
Edit FAMILIES and PACKS. A family has an id, a name, the licences it covers and a sentence for what it asks. A package has an id, a version, a licence text, its family and where it is used. The counts, the score and the explanation are worked out from the policy. Map real SPDX identifiers to your families before you rely on it.
What does a checkbox change?
It allows or blocks every package in that family. Allowed families keep their packages in Compliant; the others move to Needs review. The score is the share of packages that comply, and the header, the counts and the polite line update together.
What if nothing complies?
Untick every family and Compliant shows a short message in the same place; the page does not change height, because both tables always hold the twelve packages between them.
What stays local, and how do I wire it for real?
Everything: the packages and their licences are typed, the policy lives in the page and nothing is scanned. To make it real, read licences from your lockfile or an SBOM, store the policy where your CI can read it, and have a person confirm anything in Needs review.