@lark-apaas/client-toolkit
## 项目架构设计
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Active org package with 572 versions; maintainer rotation is expected for internal ByteDance tooling. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Maintainers follow byted.* org naming pattern; consistent with internal team expansion at ByteDance/Lark. | ai | |
| provenance | no-provenance | AI (provenance): Established package; provenance is a best-practice enhancement, not a blocker. | ai | |
| dependencies | unvetted-dep:@data-loom/js | AI (dependencies): Internal/ecosystem dep consistent with the lark-apaas/data-loom product suite this package belongs to. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-avatar | AI (dependencies): @radix-ui/react-avatar is a well-known, widely-used Radix UI primitive; stable false positive for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires in a test file on a standard globalThis polyfill pattern; not a real threat for this package. | ai | |
| phantom-deps | phantom-dep:url | AI (phantom-deps): url is a polyfill declared as dep and referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tailwindcss-animate | AI (phantom-deps): Tailwind plugin referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ant-design/cssinjs | AI (phantom-deps): Ant Design dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ant-design/colors | AI (phantom-deps): Ant Design dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:tailwind-variants | AI (phantom-deps): Tailwind utility dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:echarts | AI (phantom-deps): echarts referenced in config/storybook context; not a missing import issue. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.2.47 | 32 / 36 | |
| 1.2.46 | 32 / 36 | |
| 1.2.45 | 32 / 36 | |
| 1.2.43 | 32 / 36 | |
| 1.2.42 | 32 / 36 | |
| 1.2.37 | 32 / 36 | |
| 1.2.36 | 32 / 36 | |
| 1.2.35 | 32 / 36 | |
| 1.2.33 | 32 / 36 | |
| 1.2.32 | 32 / 36 | |
| 1.2.31 | 32 / 36 | |
| 1.2.29 | 32 / 36 | |
| 1.2.3 | 30 / 38 | |
| 1.1.31 | 28 / 38 | |
| 1.1.28 | 28 / 38 | |
| 1.1.25 | 28 / 38 | |
| 1.1.14 | 25 / 35 | |
| 1.0.21 | 21 / 35 | |
| 1.0.20 | 21 / 35 | |
| 1.0.19 | 21 / 35 | |
| 1.0.18 | 21 / 35 | |
| 1.0.17 | 21 / 35 | |
| 1.0.14 | 21 / 35 |
v1.2.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.