@weali-sdk/wx
微信公众号
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped WeChat SDK package; edit-distance match to 'pg' is a heuristic false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped WeChat SDK package; edit-distance match to 'qs' is a heuristic false positive. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is standard AES key initialization in WeChat message crypto; not obfuscation. | ai | |
| phantom-deps | phantom-dep:form-data | AI (phantom-deps): form-data is a declared runtime dep used for HTTP multipart uploads; phantom-dep heuristic misfires here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.9.8 | 4 / 0 | |
| 1.9.1 | 4 / 0 | |
| 1.9.0 | 4 / 0 | |
| 1.8.9 | 4 / 0 | |
| 1.8.8 | 4 / 0 | |
| 1.8.7 | 4 / 0 | |
| 1.8.6 | 4 / 0 | |
| 1.8.5 | 3 / 0 | |
| 1.8.4 | 3 / 0 | |
| 1.8.2 | 3 / 0 | |
| 1.8.1 | 5 / 0 |
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.