T08 · Insecure Dependencies
- Location
README.md:51- Finding
Unpinned and Unverifiable Third-Party Package Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This publishing skill matches its stated purpose, but it asks users to run unreviewed, unpinned external publisher packages that would handle API keys, local skill files, and release changes.
Install only after verifying the official package source and pinning exact versions. Use a scoped, short-lived ClawHub token, prefer dry-run or validation first, inspect local diffs before publishing, and run CI publishing in a minimal workspace with no unrelated secrets.
README.md:51Unpinned and Unverifiable Third-Party Package Execution
The README promotes publishing to ClawHub but does not clearly disclose that skill contents, metadata, and possibly bundled assets are transmitted to an external service. Users may unintentionally upload proprietary code, secrets, or sensitive documentation, especially in automated CI/CD contexts.
The README advertises automatic README modification via Gumroad link injection but does not clearly warn that local files will be edited. Silent or unexpected file mutation can lead to unintended content changes, accidental commits, or corruption of user documentation in automated workflows.
The README instructs users to run npx clawhub-publisher without pinning a specific package version, which can cause execution of whatever version is latest at invocation time. That creates a supply-chain risk: a compromised or breaking upstream release could be fetched and executed automatically in CI or on developer machines.
The skill explicitly advertises one-command publishing, deployment, changelog generation, and asset bundling to an external service, but it does not warn users that invoking it may change release state and transmit skill contents, metadata, and possibly repository-derived information off-host. In a publishing/deployment context this omission is security-relevant because users may run the skill expecting local automation, while it can perform irreversible external actions and disclose packaged artifacts or metadata.
No suspicious patterns detected.