@vertz/theme-shadcn
Shadcn-inspired theme for Vertz — pre-built style definitions using variants() and css()
2
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
viniciusdacal
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@vertz/ui | AI (dependencies): Same-monorepo sibling package at matching version; not an independent third-party risk. | ai | |
| dependencies | unvetted-dep:@vertz/ui-primitives | AI (dependencies): Same-monorepo sibling package at matching version; not an independent third-party risk. | ai | |
| provenance | no-provenance | AI (provenance): publishConfig sets provenance:true; likely a tooling/timing gap rather than intentional omission. | ai |
v0.2.73
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.