@volcengine/im-web-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/umd/main.min.js | AI (source-diff): Bundled webpack output containing base64 helper library, not obfuscated malicious payload. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata typical of internal corporate SDK, not spam. | ai | |
| provenance | missing-githead | AI (provenance): Build script removal explains missing gitHead; no malicious indicator. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.24.2 | 5 / 0 | |
| 1.22.0 | 5 / 0 | |
| 1.21.0 | 5 / 0 | |
| 1.20.1 | 5 / 0 | |
| 1.20.0 | 5 / 0 | |
| 1.19.0 | 5 / 0 | |
| 1.18.0 | 5 / 0 | |
| 1.17.0 | 5 / 29 | |
| 1.16.2 | 5 / 0 | |
| 1.16.0 | 5 / 0 | |
| 1.15.0 | 5 / 0 | |
| 1.14.0 | 5 / 0 | |
| 1.13.0 | 5 / 0 |
v1.22.0
3 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: garyyangbyte.
v1.21.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: garyyangbyte.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: garyyangbyte.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: garyyangbyte.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: garyyangbyte.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: garyyangbyte.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.