@larksuiteoapi/node-sdk No license 56 versions

@larksuiteoapi/node-sdk

npm Repository Homepage

56

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

larksuiteapimazhe.nerdwaanhappyanxinfeng.bdchenli.idevlabian.dev

Keywords

feishularksuitesdknodejs

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:base64-decode	AI (semgrep): Base64 used in standard AES-CBC decryption of event payloads, not obfuscation.	ai	2026/07/21
phantom-deps	phantom-dep:ws	AI (phantom-deps): ws is a declared runtime dep in a rollup-compiled SDK; phantom detection is a false positive due to bundled output structure.	ai	2026/04/26
phantom-deps	phantom-dep:axios	AI (phantom-deps): axios is a declared runtime dep in a rollup-compiled SDK; phantom detection is a false positive due to bundled output structure.	ai	2026/04/26
phantom-deps	phantom-dep:protobufjs	AI (phantom-deps): protobufjs is a declared runtime dep in a rollup-compiled SDK; phantom detection is a false positive due to bundled output structure.	ai	2026/04/26
phantom-deps	phantom-dep:qs	AI (phantom-deps): qs is a declared runtime dep in a rollup-compiled SDK; phantom detection is a false positive due to bundled output structure.	ai	2026/04/26
phantom-deps	phantom-dep:lodash.pickby	AI (phantom-deps): lodash.pickby is a declared runtime dep in a rollup-compiled SDK; phantom detection is a false positive due to bundled output structure.	ai	2026/04/26
phantom-deps	phantom-dep:lodash.identity	AI (phantom-deps): lodash.identity is a declared runtime dep in a rollup-compiled SDK; phantom detection is a false positive due to bundled output structure.	ai	2026/04/26
phantom-deps	phantom-dep:lodash.merge	AI (phantom-deps): lodash.merge is a declared runtime dep in a rollup-compiled SDK; phantom detection is a false positive due to bundled output structure.	ai	2026/04/26

Versions (showing 56 of 56)

Version	Deps	Published
1.71.1	7 / 27	2026-07-14
1.71.0	7 / 27	2026-07-13
1.70.0	7 / 27	2026-07-07
1.69.0	7 / 27	2026-07-07
1.68.0	7 / 27	2026-06-25
1.67.0	7 / 27	2026-06-15
1.66.1	7 / 27	2026-06-01
1.66.0	7 / 27	2026-05-26
1.65.0	7 / 27	2026-05-21
1.64.0	7 / 27	2026-05-14
1.63.1	7 / 27	2026-05-08
1.63.0	7 / 27	2026-05-08
1.62.2	7 / 27	2026-05-08
1.62.1	7 / 27	2026-04-29
1.62.0	7 / 27	2026-04-24
1.61.1	7 / 27	2026-04-21
1.61.0	7 / 27	2026-04-20
1.60.0	7 / 27	2026-03-26
1.59.0	7 / 27	2026-02-12
1.58.0	7 / 27	2026-01-30
1.57.0	7 / 27	2026-01-30
1.56.1	7 / 27	2026-01-09
1.56.0	7 / 27	2025-12-22
1.15.0	6 / 26	2023-04-06
1.14.0	6 / 26	2023-03-27
1.13.1	6 / 26	2023-03-23
1.13.0	6 / 26	2023-03-22
1.12.0	6 / 26	2023-02-22
1.11.1	6 / 26	2023-02-17
1.11.0	6 / 26	2023-02-08
1.10.0	6 / 26	2023-01-30
1.9.0	6 / 26	2023-01-20
1.8.1	6 / 26	2023-01-12
1.8.0	6 / 26	2022-12-20
1.7.1	6 / 26	2022-11-24
1.7.0	6 / 26	2022-11-24
1.6.3	6 / 26	2022-11-09
1.6.2	6 / 26	2022-11-09
1.6.1	6 / 26	2022-11-08
1.6.0	6 / 26	2022-11-07
1.5.0	6 / 26	2022-10-24
1.4.1	6 / 26	2022-10-18
1.4.0	6 / 26	2022-10-11
1.3.0	6 / 26	2022-10-10
1.2.3	6 / 21	2022-09-29
1.2.2	6 / 21	2022-09-28
1.2.1	6 / 19	2022-09-26
1.2.0	6 / 19	2022-09-23
1.1.0	6 / 19	2022-08-31
1.0.7	6 / 19	2022-08-19
1.0.6	6 / 19	2022-08-18
1.0.5	6 / 12	2022-08-09
1.0.4	6 / 12	2022-08-09
1.0.3	6 / 12	2022-08-03
1.0.2	6 / 12	2022-08-03
1.0.1	6 / 12	2022-08-03

v1.71.1

1 finding

LOW No provenance attestation provenance

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

v1.71.0

1 finding

LOW No provenance attestation provenance

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

v1.70.0

1 finding

LOW No provenance attestation provenance

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

v1.69.0

1 finding

LOW No provenance attestation provenance

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

v1.60.0

1 finding

LOW No provenance attestation provenance

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

v1.59.0

1 finding

LOW No provenance attestation provenance

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

v1.58.0

1 finding

LOW No provenance attestation provenance

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

v1.57.0

1 finding

LOW No provenance attestation provenance

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

v1.56.1

1 finding

LOW No provenance attestation provenance

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

v1.56.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.15.0

1 finding

LOW No provenance attestation provenance

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

v1.14.0

1 finding

LOW No provenance attestation provenance

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

v1.13.1

1 finding

LOW No provenance attestation provenance

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

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.1

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.1

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

LOW No provenance attestation provenance

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

v1.7.1

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.3

1 finding

LOW No provenance attestation provenance

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

v1.6.2

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.1

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.