@wecom/wecom-openclaw-plugin
OpenClaw WeCom (企业微信) channel plugin (official by Tencent WeCom team)
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Official WeCom team package; provenance not yet enabled in their CI but no other risk signals present. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dependency; phantom-dep fires because it's not directly imported in the entry point, not a real issue. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 2026.5.25 | 5 / 0 | |
| 2026.5.14 | 5 / 0 | |
| 2026.5.7 | 5 / 0 | |
| 2026.4.2201 | 5 / 0 | |
| 2026.4.29 | 5 / 0 | |
| 2026.4.27 | 5 / 0 | |
| 2026.4.23 | 5 / 0 | |
| 2026.4.22 | 5 / 0 | |
| 2026.4.8 | 5 / 0 | |
| 2026.4.3 | 5 / 0 | |
| 2026.4.2 | 2 / 0 | |
| 2026.4.1 | 2 / 0 | |
| 2026.3.30 | 2 / 0 | |
| 2026.3.26 | 2 / 0 | |
| 2026.3.25 | 2 / 0 | |
| 2026.3.24 | 2 / 0 | |
| 2026.3.20 | 2 / 0 | |
| 1.0.13 | 2 / 0 | |
| 1.0.12 | 2 / 0 | |
| 1.0.11 | 2 / 0 | |
| 1.0.10 | 2 / 0 | |
| 1.0.9 | 2 / 0 | |
| 1.0.8 | 2 / 0 | |
| 1.0.6 | 2 / 9 | |
| 1.0.5 | 2 / 9 | |
| 1.0.4 | 2 / 9 | |
| 1.0.3 | 2 / 9 | |
| 1.0.0 | 2 / 9 |
v2026.5.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.4.2201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.4.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.4.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2026.3.26
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: wecom-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.