dingtalk-jsapi
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:gdt/api/openApiObj.js | AI (source-diff): Minified compiled TS module graph, no malicious behavior. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Modularized per-API file structure for large SDK, not injected code. | ai | |
| source-diff | obfuscated-file:constant/apiMapping.js | AI (source-diff): Minified TS-compiled data mapping, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:gdt/api/apiObj.js | AI (source-diff): Minified TS-compiled API index, no malicious behavior. | ai | |
| source-diff | obfuscated-file:gdt/api/biz/contact/departmentsPicker.js | AI (source-diff): Standard TS compiler helpers, bundled build output. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 3.2.9 | 1 / 0 | |
| 3.2.8 | 1 / 0 | |
| 3.2.7 | 1 / 0 | |
| 3.2.5 | 1 / 0 | |
| 3.2.2 | 1 / 0 | |
| 3.2.1 | 1 / 0 | |
| 3.2.0 | 1 / 0 | |
| 3.1.4 | 1 / 0 | |
| 3.1.3 | 1 / 0 | |
| 3.1.2 | 1 / 0 | |
| 3.1.1 | 1 / 0 | |
| 3.1.0 | 1 / 0 | |
| 3.0.45 | 1 / 0 | |
| 3.0.43 | 1 / 0 | |
| 3.0.41 | 1 / 0 | |
| 3.0.38 | 1 / 0 | |
| 3.0.36 | 1 / 0 | |
| 3.0.35 | 1 / 0 | |
| 3.0.3 | 1 / 0 | |
| 3.0.2 | 1 / 0 |
v3.0.45
3 findingsThis version was published by a different npm account than previous versions on 2025-01-14. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.43
6 findingsThis version was published by a different npm account than previous versions on 2025-01-13. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.41
5 findingsThis version was published by a different npm account than previous versions on 2024-10-28. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.