← Home

@volcengine/openclaw-volcengine-rtc

OpenClaw VolcEngine channel plugin

13
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

zhang6464jjjkkkaaabytednpmvcloud_fezhouykboya1127kongfanzizhangjing.2037msq17huangkaisheng.0x0vikinglbxkaijie_bytediyijieniguitangjinwei123xiongxiong.001shushushuluofan.0406yanzhen.0756ash.yuchenyunfei.csyuhuajian.1yunyi_6512ethan.bytetiebytewangmengyuanxuguoqingvolc-iaas-test01volc-iaasxiujie.1zhuhongshuyu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): child_process used in CLI installer binary; consistent with plugin install tooling for this package. ai
semgrep semgrep:base64-decode AI (semgrep): Decodes JPEG snapshot image data into a buffer for media saving — not a payload hiding pattern. ai

Versions (showing 13 of 13)

Version Deps Published
2026.4.12 1 / 0
2026.4.11 1 / 0
2026.4.10 1 / 0
2026.4.9 1 / 0
2026.4.8 1 / 0
2026.4.5 1 / 0
2026.4.2 1 / 0
2026.4.1 1 / 0
2026.3.31 1 / 0
2026.3.28 1 / 0
2026.3.24 1 / 0
2026.3.23 1 / 0
2026.3.13 1 / 0

v2026.4.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.4.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.4.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.4.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.4.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.4.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.3.31

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.3.28

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.3.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.3.23

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2026.3.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.