Clawsite
AdvisoryAudited by Static analysis on May 11, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken deploy could remove or replace files on the live public site.
The primary deploy action can overwrite the public site and remove previously hosted files if they are missing from the new zip. This is disclosed and aligned with static hosting, but it is a meaningful mutation capability.
Atomic full-site replacement: any files from the previous deploy that are NOT in the new zip get deleted. Deploy = full snapshot, not incremental upload.
Review the files being zipped before deployment, keep a backup for important sites, and require explicit confirmation before using destructive operations such as full replacement or site deletion.
Anyone or any agent with the API key could modify, purge, list, or delete the associated Clawsite resources allowed by that key.
The skill needs a Clawsite bearer token and site ID to call authenticated hosting endpoints. This is expected for the service, but the key grants authority over the hosted site.
`CLAWSITE_API_KEY` | required | Bearer token for all authenticated endpoints (`csk_live_*` format)
Store the API key only in the intended environment, avoid printing it in logs or public pages, and rotate/revoke it if it may have been exposed.
If private files, secrets, drafts, or user data are included in the zip, they may become publicly accessible on the hosted site.
The skill sends selected site files to the Clawsite provider and serves them publicly. That data flow is the stated purpose, but users should notice that uploaded files become public.
deploy a zip of HTML / CSS / JS / images in one API call ... wants to share it as a public URL
Only deploy a reviewed static-site directory, exclude secrets and private files, and treat the resulting Clawsite URL as public.