← Home

@sp1in/wechat-gateway

npm Repository Homepage

Unified WeChat gateway — single QR login, switch AI CLI via /claude /kimi /qwen /iflow

10
Versions
MIT
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

sp1in

Keywords

wechatgatewayclaudekimiqweniflowbridge

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): env copy is used to pass environment to child process backends; not exfiltration, stable pattern for this package. ai

Versions (showing 10 of 10)

Version Deps Published
0.3.0 2 / 2
0.2.1 2 / 2
0.2.0 2 / 2
0.1.6 2 / 2
0.1.5 2 / 2
0.1.4 2 / 2
0.1.3 2 / 2
0.1.2 2 / 2
0.1.1 2 / 2
0.1.0 2 / 2

v0.3.0

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.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.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.

v0.1.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.

v0.1.0

2 findings
HIGH env-spread: src/index.ts:102 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/PXSR/wechatanybot/blob/eb1032898f16f7d8a4f06d66abd0f7b0012ebc6c/src/index.ts#L102 100 | }; 101 | > 102 | const env: Record<string, string | undefined> = { ...process.env }; 103 | // kimi/qwen 基于 Python，强制 UTF-8 104 | if (backend === 'kimi' || backend === 'qwen') {

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.