Trust signals
Why this verdict
PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.
- Versions published
- 1
- First published
- Jun 2026
- Publisher
- anuragsingkk
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
Block this release in CIcurl · GitHub Actions
Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer $PKGRADAR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"specs":["@anuragsingk/[email protected]"],"fail_on":"review"}'GitHub Actions step:
- name: PkgRadar gate
run: |
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
-H "Content-Type: application/json" \
-d '{"specs":["@anuragsingk/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Credential file access: matched "id_rsa"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk review · score 10 · status changed
Evidence
Static findings
2 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 2 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/dist/security/AISecurityScanner.js | matched "id_rsa" | 5 |
| low | Credential file access | package/src/security/AISecurityScanner.ts | matched "id_rsa" | 5 |
Manifest
Package metadata
Scripts71
buildtsc && tsc-aliasbuild:watchtsc --watchcheck:cinpm run typecheck && npm run lint && npm run test:coveragecheck:ignorenode scripts/sync-ignore-files.jsdevnpm run build && DEBUG=true node dist/index.jsdocker:builddocker build -t docdyhr/mcp-wordpress:latest .docker:publish./scripts/manual-docker-publish.shdocs:generatenpm run build && node scripts/generate-docs.jsdocs:servenpm run docs:generate && node scripts/serve-docs.jsdocs:validatenpm run docs:generate && node scripts/validate-docs.jsdocs:watchnpm run docs:generate && echo 'Watching for changes...' && npm run docs:servedoctor:vscodenpm run test:vscode && echo ' 🩺 VS Code health check complete'dxt:cleanrm -rf dxt-build mcp-wordpress.dxt minimal-dxt-build mcp-wordpress-minimal.dxt mcp-wordpress-official.dxtdxt:packagenpm run dxt:clean && npm run dxt:builddxt:package:officialnpm run build && node scripts/build-dxt-clean.cjsevalnpm run build && npx mcp-eval evaluations/config/wordpress-tools-eval.yaml dist/index.jseval:reportnode evaluations/scripts/generate-report.jsfix:rest-authbash scripts/fix-rest-api-auth.shformatprettier --write *.md docs/**/*.md src/**/*.ts tests/**/*.tsformat:checkprettier --check *.md docs/**/*.md src/**/*.ts tests/**/*.tshealthnode scripts/health-check.jslinteslint src/ tests/lint:fixeslint src/ tests/ --fixlint:mdmarkdownlint *.md docs/**/*.mdlint:md:fixmarkdownlint *.md docs/**/*.md --fixpre-commitlint-stagedpreparehuskyprepublishOnlynpm run build && npm run check:ignorereleasesemantic-releaserelease:drysemantic-release --dry-run- …and 41 more.
Dependencies5
@modelcontextprotocol/sdk^1.29.0dotenv^17.3.1form-data^4.0.5googleapis^171.4.0zod^4.3.6