@larksuiteoapi/node-sdk
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 |
|---|---|---|---|---|
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.66.1 | 7 / 27 | |
| 1.66.0 | 7 / 27 | |
| 1.65.0 | 7 / 27 | |
| 1.64.0 | 7 / 27 | |
| 1.63.1 | 7 / 27 | |
| 1.63.0 | 7 / 27 | |
| 1.62.2 | 7 / 27 | |
| 1.62.1 | 7 / 27 | |
| 1.62.0 | 7 / 27 | |
| 1.61.1 | 7 / 27 | |
| 1.61.0 | 7 / 27 |
v1.66.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.