openclaw-bottle-drift

v1.0.0

面向 OpenClaw 节点的互动式漂流瓶 Skill。支持网页控制台、在线用户心跳、随机投递、专属回复链接与回信收取。

0· 114·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description match the included server, CLI and web UI. Required binary (python3), files (scripts/resources) and SQLite persistence are expected for a local relay/dashboard; nothing in metadata or files asks for unrelated cloud credentials or system access.
Instruction Scope
SKILL.md instructs running a local HTTP relay and using the web dashboard or CLI. The runtime instructions and code stay within the stated feature set. One notable runtime capability: users can provide callback_url values (webhooks) that the relay may call — this is expected for notifications but is an outbound network capability you should consider before exposing the service publicly.
Install Mechanism
No install spec or third‑party packages; code uses Python standard library only and no downloads or archive extraction. This minimizes install-side risk.
Credentials
The bundle requires no environment variables or credentials — consistent with a self‑hosted local relay. However, the system accepts user-provided callback_url and generates reply links/tokens; those URLs and tokens are sensitive and could be used to trigger outbound requests or to leak data if misused. The SKILL.md and README acknowledge these concerns.
Persistence & Privilege
Skill does not request elevated or persistent platform privileges (always:false). It stores data in a local SQLite DB in the bundle directory and keeps small client state in browser localStorage — expected for this app and limited in scope.
Assessment
This skill appears to be what it claims: a self‑hosted Bottle Drift relay with a web dashboard and CLI, implemented using Python standard library and SQLite. Before installing or exposing it publicly, consider: - Review the relay_server.py full source (especially the parts that perform deliveries and any code that performs HTTP POSTs to user callback_url) to confirm there are no unexpected outbound calls, redirects, or arbitrary command execution. The provided snippet shows expected behavior but parts were truncated in the review bundle, so verifying the entire file will raise confidence. - If you will open the relay to a network, use HTTPS, reverse proxy, auth and rate limiting. The README advises this; follow it. - Treat reply_url tokens and callback_url destinations as sensitive: do not publish tokens publicly and restrict who can set callback URLs to avoid them being used as an exfiltration or SSRF vector. - Keep the SQLite DB file in a safe location and back it up if needed; be aware it contains user IDs, messages and reply metadata. - Test locally first (127.0.0.1) and inspect logs/traffic to ensure only expected outbound requests occur. If you want higher assurance, provide the full untruncated relay_server.py for a line-by-line audit (to confirm delivery, webhook and reply handling are implemented as described and no hidden network/exec behavior exists).

Like a lobster shell, security has layers — review code before you run it.

latestvk97a8zcchx4nr1jr4kvyss9v51833xtb

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🍾 Clawdis
Any binpython3

Comments