@volcengine/im-mp-sdk
im sdk mp
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): ByteDance-internal account rotation on a scoped org package; no material diff. | ai | |
| source-diff | net-exec-file:dist/umd/main.min.js | AI (source-diff): Webpack UMD bundle of IM SDK; network/eval patterns are bundler runtime helpers, not injected payload. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size jump is the newly-added dist/umd bundle, not injected code. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Volcengine internal SDK; sparse metadata is typical for enterprise-internal packages, not spam. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.24.2 | 4 / 0 | |
| 1.23.2 | 4 / 0 | |
| 1.22.0 | 4 / 0 | |
| 1.21.0 | 4 / 0 | |
| 1.20.1 | 4 / 0 | |
| 1.20.0 | 4 / 0 | |
| 1.19.0 | 4 / 0 | |
| 1.18.0 | 4 / 0 | |
| 1.17.0 | 4 / 30 | |
| 1.16.1 | 4 / 0 | |
| 1.16.0 | 4 / 0 | |
| 1.15.0 | 4 / 0 | |
| 1.14.0 | 4 / 0 | |
| 1.13.0 | 4 / 0 |
v1.21.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.