@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@data-loom/js | AI (dependencies): Small utility dep, no material change across versions, no malicious behavior evidenced. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): crypto-js/blueimp-md5 are well-known hashing libs, no exfil behavior found | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer roster change, no new suspicious publisher added | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-avatar | AI (phantom-deps): UI component library pattern; stable false positive for this package. | ai | |
| 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:class-variance-authority | 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: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 |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.1.20 | 16 / 10 | |
| 1.1.19 | 16 / 10 | |
| 1.1.18 | 16 / 10 | |
| 1.1.17 | 16 / 10 | |
| 1.1.16 | 16 / 10 | |
| 1.1.15 | 16 / 10 | |
| 1.1.14 | 16 / 10 | |
| 1.1.13 | 16 / 10 | |
| 1.1.12 | 16 / 10 | |
| 1.1.11 | 16 / 10 | |
| 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 | |
| 1.1.4 | 14 / 10 | |
| 1.1.3 | 14 / 10 | |
| 1.1.2 | 14 / 10 | |
| 1.1.1 | 14 / 10 | |
| 1.1.0 | 14 / 10 | |
| 1.0.1 | 12 / 8 | |
| 1.0.0 | 12 / 8 | |
| 0.0.3 | 12 / 8 | |
| 0.0.2 | 12 / 8 | |
| 0.0.1 | 12 / 8 |
v1.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.