@volcengine/im-sdk-core
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): SDK core package in established @volcengine org; sparse metadata is a style choice, not a spam/malware indicator. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.24.2 | 5 / 0 | |
| 1.23.2 | 5 / 0 | |
| 1.22.0 | 5 / 0 | |
| 1.16.1 | 5 / 0 | |
| 1.15.0 | 5 / 0 | |
| 1.14.0 | 5 / 0 | |
| 1.13.0 | 5 / 0 |
v1.16.1
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.