@lark-apaas/client-toolkit-lite
Lightweight client toolkit for Express/Vite tech stack - hooks, utils, and UI components without SDK integrations
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@radix-ui/react-avatar | AI (dependencies): @radix-ui/react-avatar is a well-known, widely-used Radix UI primitive with no known malicious history. | ai | |
| phantom-deps | phantom-dep:lucide-react | AI (phantom-deps): UI component library pattern; deps referenced in config/barrel files, not a real phantom-dep concern. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-slot | AI (phantom-deps): UI component library pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-avatar | AI (phantom-deps): UI component library pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-tooltip | AI (phantom-deps): UI component library pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:class-variance-authority | AI (phantom-deps): UI component library pattern; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.1.10 | 16 / 10 | |
| 1.1.9 | 15 / 10 | |
| 1.1.8 | 16 / 10 | |
| 1.1.7 | 15 / 10 | |
| 1.1.6 | 14 / 10 | |
| 1.1.5 | 14 / 10 | |
| 0.0.3 | 12 / 8 |
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.