wordpress-receipts@0.1.6
VERIFIED· install onlyPublisher claims: "Publish WordPress posts with API and public URL receipts." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 3 of 3 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What changed since 0.1.3
vet-skills diff wordpress-receipts 0.1.3 0.1.6This version reaches for something 0.1.3 did not: 3 new credential variables (WORDPRESS_APPLICATION_PASSWORD, WORDPRESS_APP_PASSWORD, WORDPRESS_AUTHOR_ID). Compared from the two recorded runs, not from source.
- New credential variables
- WORDPRESS_APPLICATION_PASSWORD, WORDPRESS_APP_PASSWORD, WORDPRESS_AUTHOR_ID
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-22 and scored it 85/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
--env-file .env.wordpress \Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.node scripts/wp-verify-receipt.js --env-file .env.wordpress --id 456Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log(JSON.stringify({ ok: true, action: 'draft-created', id: post.id, status: verified.status, title, link: verified.link, publicStatus: null }, null, 2));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…hod: 'GET', ...requestOptions() }); const ok = publicRes.status === 200; console.log(JSON.stringify({ ok, action: 'published', id: post.id, status: verified.status, author: verified.author, categories: verified.cate…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(JSON.stringify({ ok, id: post.id, date: post.date, status: post.status, title: post.title?.rendered, link: url, publicStatus: publicRes.status }, null, 2));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.node scripts/wp-verify-receipt.js --env-file .env.wordpress --id 456 --url https://example.com/post-slug/Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.node scripts/wp-verify-receipt.js --env-file .env.wordpress --date 2026-07-01Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.return Response.json(post);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.--env-file .env.wordpress \Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if (url.includes('/posts?')) return Response.json(scenario === 'duplicate-failure' ? [post] : []);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.return Response.json(post);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.