@polymarbot/nuxt-layer-shadcn-ui
Nuxt layer providing shadcn-vue based UI components
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Nuxt layer re-exports UI components; phantom deps are expected in this pattern. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): Nuxt layer re-exports UI components; phantom deps are expected in this pattern. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Nuxt layer re-exports UI components; phantom deps are expected in this pattern. | ai | |
| phantom-deps | phantom-dep:@tailwindcss/postcss | AI (phantom-deps): Nuxt layer re-exports UI components; phantom deps are expected in this pattern. | ai | |
| phantom-deps | phantom-dep:qrcode | AI (phantom-deps): Nuxt layer registers deps via config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Nuxt layer registers deps via config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Nuxt layer registers deps via config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@types/qrcode | AI (phantom-deps): Type-only package; framework-scoped, loaded by convention. | ai | |
| phantom-deps | phantom-dep:tw-animate-css | AI (phantom-deps): Nuxt layer registers deps via config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:lucide-vue-next | AI (phantom-deps): Nuxt layer registers deps via config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@types/lodash-es | AI (phantom-deps): Type-only package; framework-scoped, loaded by convention. | ai | |
| phantom-deps | phantom-dep:@vuepic/vue-datepicker | AI (phantom-deps): Nuxt layer registers deps via config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@polymarbot/nuxt-layer-effect | AI (phantom-deps): Same-org Nuxt layer dep; loaded by convention, not direct import. | ai |
Versions (showing 51 of 86)
| Version | Deps | Published |
|---|---|---|
| 0.12.2 | 14 / 0 | |
| 0.12.1 | 14 / 0 | |
| 0.12.0 | 14 / 0 | |
| 0.11.17 | 14 / 0 | |
| 0.11.16 | 14 / 0 | |
| 0.11.15 | 14 / 0 | |
| 0.11.13 | 14 / 0 | |
| 0.11.12 | 14 / 0 | |
| 0.11.11 | 14 / 0 | |
| 0.11.10 | 14 / 0 | |
| 0.11.9 | 14 / 0 | |
| 0.11.8 | 14 / 0 | |
| 0.11.7 | 14 / 0 | |
| 0.11.6 | 14 / 0 | |
| 0.11.5 | 14 / 0 | |
| 0.11.4 | 14 / 0 | |
| 0.11.3 | 14 / 0 | |
| 0.11.2 | 14 / 0 | |
| 0.11.1 | 14 / 0 | |
| 0.11.0 | 14 / 0 | |
| 0.10.3 | 14 / 0 | |
| 0.10.2 | 14 / 0 | |
| 0.10.1 | 14 / 0 | |
| 0.10.0 | 14 / 0 | |
| 0.9.6 | 14 / 0 | |
| 0.9.5 | 14 / 0 | |
| 0.9.4 | 14 / 0 | |
| 0.9.3 | 14 / 0 | |
| 0.9.2 | 14 / 0 | |
| 0.9.1 | 14 / 0 | |
| 0.9.0 | 14 / 0 | |
| 0.8.8 | 14 / 0 | |
| 0.8.7 | 14 / 0 | |
| 0.8.6 | 14 / 0 | |
| 0.8.5 | 14 / 0 | |
| 0.8.4 | 14 / 0 | |
| 0.8.3 | 14 / 0 | |
| 0.8.2 | 14 / 0 | |
| 0.8.1 | 14 / 0 | |
| 0.8.0 | 14 / 0 | |
| 0.7.7 | 14 / 0 | |
| 0.7.6 | 14 / 0 | |
| 0.7.5 | 14 / 0 | |
| 0.7.4 | 14 / 0 | |
| 0.7.3 | 14 / 0 | |
| 0.7.2 | 14 / 0 | |
| 0.7.1 | 14 / 0 | |
| 0.7.0 | 14 / 0 | |
| 0.6.4 | 14 / 0 | |
| 0.6.3 | 14 / 0 | |
| 0.6.2 | 14 / 0 |
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.