PublishGuard — Post Verification & Credential Manager

Prevents false "posted successfully" claims by verifying content URLs, enforcing platform rules, tracking rate limits, and securely storing credentials persi...

Do not install or store live credentials yet. The package claims "never stored in plaintext" but the main engine writes credentials to a plaintext JSON file in the workspace. Before using: (1) Ask the maintainer to explain why publish_guard.py includes CredentialStore that saves plaintext and whether that is intentional or a leftover; (2) If you must test, do so in an isolated sandbox and do not enter real secrets; (3) Prefer using the EncryptedVault and run the provided migrate tool, but verify that publish_guard actually reads from the encrypted vault rather than the plaintext file; (4) If you intend to use this in production, request the author remove (or gate) the plaintext store, or modify the code to use only the encrypted vault with secure permissions and documented migration behavior; (5) Confirm the vault's cryptography and threat model meet your security needs — the vault implements custom crypto primitives (HMAC-CTR, PBKDF2) and makes specific machine-binding choices that you may want reviewed by a crypto expert.

Type: OpenClaw Skill Name: publish-guard Version: 1.1.0 The skill bundle is classified as suspicious due to a critical security vulnerability in `scripts/publish_guard.py`. While `SKILL.md` and `scripts/vault_crypto.py` describe and implement robust, machine-bound encryption for credentials, the main `PublishGuard` class in `scripts/publish_guard.py` uses an unencrypted `CredentialStore` that saves sensitive API keys and tokens in plaintext JSON files on disk. This directly contradicts the stated security features and exposes credentials to local file system access, representing a severe flaw that allows for data compromise.