⚠️ Supply Chain Risk Detected

This PR contains patterns commonly associated with supply chain attacks. This does not mean the PR is malicious — but these patterns require careful human review before merging.

⚠️ WARNING: base64 encoding/decoding detected

Base64 has legitimate uses (images, JWT, etc.) but is also commonly used to obfuscate malicious payloads. Verify the usage is appropriate.

Matches (first 20):

825:+    return base64.b64encode(str(value).encode("utf-8")).decode("ascii")
973:+    decoded = base64.b64decode(aes_key_b64)
1912:+                and base64.b64encode(bytes.fromhex(str((item.get("image_item") or {}).get("aeskey")))).decode("ascii")
2175:+            aes_key_b64=base64.b64encode(aes_key).decode("ascii"),

Automated scan triggered by supply-chain-audit. If this is a false positive, a maintainer can approve after manual review.

⚠️ Supply Chain Risk Detected

This PR contains patterns commonly associated with supply chain attacks. This does not mean the PR is malicious — but these patterns require careful human review before merging.

⚠️ WARNING: base64 encoding/decoding detected

Base64 has legitimate uses (images, JWT, etc.) but is also commonly used to obfuscate malicious payloads. Verify the usage is appropriate.

Matches (first 20):

837:+    return base64.b64encode(str(value).encode("utf-8")).decode("ascii")
985:+    decoded = base64.b64decode(aes_key_b64)
1924:+                and base64.b64encode(bytes.fromhex(str((item.get("image_item") or {}).get("aeskey")))).decode("ascii")
2187:+            aes_key_b64=base64.b64encode(aes_key).decode("ascii"),

⚠️ WARNING: Install hook files modified

These files can execute code during package installation or interpreter startup.

Files:

hermes_cli/setup.py

Automated scan triggered by supply-chain-audit. If this is a false positive, a maintainer can approve after manual review.

Nice to see WeChat land! I had an earlier adapter PR open at #2502 (March 22, iLink 2.1.7 protocol) that went through a few review rounds — happy to see the feature ship either way.

I can help test this on a Raspberry Pi 4B (aarch64, Raspberry Pi OS) with a real WeChat account if that's useful. Already have a gateway running on it with Telegram + frp tunneling, so spinning up a Weixin adapter alongside would be straightforward.

Anything specific you'd want validated beyond the basic send/receive flow?

I would like to report a significant change in the output format on WeChat following the recent upgrade. The formatting has shifted from a cohesive, structured table to fragmented, individual message bubbles, which significantly impacts readability.

I would like to report a significant change in the output format on WeChat following the recent upgrade. The formatting has shifted from a cohesive, structured table to fragmented, individual message bubbles, which significantly impacts readability.

I'm going to fix it :）

Very cool!!!
I think it’s very stable.
But how can I introduce Hermes to a second user? Right now, the bot can’t be added or accessed by other users.

it does not support wechat group yet?it's confusing in settings