← Home

@lark-apaas/client-toolkit

npm

## 项目架构设计

41
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

bytednpmfengtianran_bytedxiaochuanzhang_bytedbyted.lycoirefduanlikang_byteyanmingjiangyh_xyuki-bytedanceaihao.0331chengshihao1

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): Added deps are first-party @lark-apaas/* SDKs; expected for this toolkit. ai
source-diff large-new-source-files AI (source-diff): Large React component toolkit; new source files are normal growth. ai
source-diff obfuscated-file:lib/logger/source-map-mappings-wasm.d.ts AI (source-diff): WASM hex dump from source-map package, not obfuscated malicious code. ai
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:tailwindcss-animate AI (phantom-deps): Tailwind plugin referenced in config; stable false positive. 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:@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
phantom-deps phantom-dep:@ant-design/cssinjs AI (phantom-deps): Ant Design dep referenced in config; stable false positive. ai

Versions (showing 41 of 41)

Version Deps Published
1.2.61 32 / 36
1.2.60 32 / 36
1.2.59 32 / 36
1.2.58 32 / 36
1.2.57 32 / 36
1.2.56 32 / 36
1.2.55 32 / 36
1.2.54 32 / 36
1.2.53 32 / 36
1.2.52 32 / 36
1.2.51 32 / 36
1.2.50 32 / 36
1.2.49 32 / 36
1.2.48 32 / 36
1.2.47 32 / 36
1.2.46 32 / 36
1.2.45 32 / 36
1.2.44 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.20 31 / 36
1.2.9 30 / 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.1.0 24 / 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.61

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.60

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.59

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.58

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.57

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.56

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.44

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.20

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: fengtianran_byted → duanlikang_byte (on 2026-03-10, known maintainer) provenance

This version was published by a different npm account (duanlikang_byte) than the most recent previously approved version (fengtianran_byted) on 2026-03-10, but duanlikang_byte is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.2.9

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: fengtianran_byted → duanlikang_byte (on 2026-01-29, known maintainer) provenance

This version was published by a different npm account (duanlikang_byte) than the most recent previously approved version (fengtianran_byted) on 2026-01-29, but duanlikang_byte is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.0

3 findings
HIGH New obfuscated file: lib/logger/source-map-mappings-wasm.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: yanmingjiang → fengtianran_byted (on 2025-11-05, known maintainer) provenance

This version was published by a different npm account (fengtianran_byted) than the most recent previously approved version (yanmingjiang) on 2025-11-05, but fengtianran_byted is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.