@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, 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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 used in standard AES-CBC decryption of event payloads, not obfuscation. | 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: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: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 | |
| 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 |
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 1.71.1 | 7 / 27 | |
| 1.71.0 | 7 / 27 | |
| 1.70.0 | 7 / 27 | |
| 1.69.0 | 7 / 27 | |
| 1.68.0 | 7 / 27 | |
| 1.67.0 | 7 / 27 | |
| 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 | |
| 1.60.0 | 7 / 27 | |
| 1.59.0 | 7 / 27 | |
| 1.58.0 | 7 / 27 | |
| 1.57.0 | 7 / 27 | |
| 1.56.1 | 7 / 27 | |
| 1.56.0 | 7 / 27 | |
| 1.15.0 | 6 / 26 | |
| 1.14.0 | 6 / 26 | |
| 1.13.1 | 6 / 26 | |
| 1.13.0 | 6 / 26 | |
| 1.12.0 | 6 / 26 | |
| 1.11.1 | 6 / 26 | |
| 1.11.0 | 6 / 26 | |
| 1.10.0 | 6 / 26 | |
| 1.9.0 | 6 / 26 | |
| 1.8.1 | 6 / 26 | |
| 1.8.0 | 6 / 26 | |
| 1.7.1 | 6 / 26 | |
| 1.7.0 | 6 / 26 | |
| 1.6.3 | 6 / 26 | |
| 1.6.2 | 6 / 26 | |
| 1.6.1 | 6 / 26 | |
| 1.6.0 | 6 / 26 | |
| 1.5.0 | 6 / 26 | |
| 1.4.1 | 6 / 26 | |
| 1.4.0 | 6 / 26 | |
| 1.3.0 | 6 / 26 | |
| 1.2.3 | 6 / 21 | |
| 1.2.2 | 6 / 21 | |
| 1.2.1 | 6 / 19 | |
| 1.2.0 | 6 / 19 | |
| 1.1.0 | 6 / 19 | |
| 1.0.7 | 6 / 19 | |
| 1.0.6 | 6 / 19 |
v1.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.