Lines 242-282markdown
243- Files: `scripts/validate-links.sh`, `docs_zh-CN/link-validation-report.txt`
244- Evidence: `scripts/validate-links.sh` writes `docs_zh-CN/link-validation-report.txt` with a timestamp and absolute local paths. The script labels this as a translated report but scans `docs/`, not `docs_zh-CN/`, and resolves internal links by basename only. The script itself notes that links such as `../../CATALOG.md` can be false positives.
245- Risk: rerunning the script creates non-portable tracked drift and produces a report that can mix real broken links with known false positives.
246- Suggested fix: either make the report deterministic and unambiguous, or stop tracking it. Resolve links relative to each source file and run separate checks for canonical docs and translated docs.
248### Low - deliberate pipe-to-shell examples remain allowlisted
250Resolved in follow-up patch: executable `curl|bash`, `curl|sh`, and `irm|iex` install examples in canonical skill sources were replaced with package-manager or download-inspect-execute flows, and obsolete pipe-to-shell allowlists were removed. The remaining `security-allowlist` comments cover non-pipe rule families or sandbox notes.
252- Files include `skills/bun-development/SKILL.md`, `skills/linkerd-patterns/SKILL.md`, `skills/cloud-penetration-testing/SKILL.md`, `skills/varlock/SKILL.md`, `skills/evolution/SKILL.md`, and plugin mirrors.
253- Evidence: `npm run security:docs` passes because these examples are allowlisted, but the repo still contains executable `curl|bash`, `curl|sh`, and `irm|iex` examples.
254- Risk: this is accepted by current policy, but remains risky guidance for automated agents.
255- Suggested fix: where practical, replace executable pipe-to-shell examples with package-manager or checksum-verified alternatives; keep allowlists only where no safe practical alternative exists.
257### Low - documentation examples use realistic-looking secret placeholders
259Resolved in follow-up patch: canonical examples now use `<AWS_ACCESS_KEY_ID>`, `<AWS_SECRET_ACCESS_KEY>`, and `<BASE64_PRIVATE_KEY>`, and `npm run security:docs` blocks those realistic placeholder patterns from returning.
261- Files include `skills/comfyui-gateway/references/integration.md`, `skills/security/aws-iam-best-practices/SKILL.md`, `skills/k8s-manifest-generator/resources/implementation-playbook.md`, and plugin mirrors.
262- Evidence: secret-pattern scanning found `AKIAIOSFODNN7EXAMPLE`, `wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY`, and `-----BEGIN PRIVATE KEY-----` examples. These are not confirmed live secrets: the AWS values are standard examples and the private key block is an ellipsis placeholder.
CriticalCritical Secret
Package contains a critical-looking secret pattern.
bundled-skills/docs/maintainers/full-repo-audit-2026-05-23.mdView on unpkg · L262 263- Risk: realistic secret-looking examples can create noisy secret-scan alerts and make it harder to distinguish documentation placeholders from real leaks.
264- Suggested fix: replace realistic credential examples with unmistakable placeholders such as `<AWS_ACCESS_KEY_ID>`, `<AWS_SECRET_ACCESS_KEY>`, and `<BASE64_PRIVATE_KEY>`.
266## Non-findings / bounded checks
268- The apparent `--- ` frontmatter prefix in eight skills is accepted by the repo parser (`^---\s*\n`) and those skills are indexed, so this is not currently a validator bug.
269- Duplicate names under `skills/.disabled` are intentionally skipped by validator/index generation.
270- Root npm production audit reported `0 vulnerabilities`.
271- Root, web app, and data package moderate audits reported `0 vulnerabilities`.
272- Loki todo-app frontend and backend moderate audits reported `0 vulnerabilities`.
273- Loki todo-app frontend and backend builds completed successfully.
274- Telegram and WhatsApp Node boilerplates compile successfully when installed in temp copies.
275- WhatsApp Node boilerplate moderate audit reported `0 vulnerabilities` in a temp copy.
276- Python syntax checking found 0 errors across 1077 source files.
277- Shell syntax checking found 0 errors across 61 shell scripts.
278- JavaScript syntax checking found 0 errors across 74 source files.
279- YAML and XML-family parse checks found 0 syntax errors in tracked files.
280- The 7 tracked symlinks all resolve to in-repo targets.
281- The strict JSON parse failures are JSONC/commented config files rather than malformed runtime JSON; TypeScript accepts `tsconfig.json` comments, and the commented `tsconfig-strict.json` is a reference artifact mirrored byte-for-byte.
282- Plugin mirror skill files are byte-for-byte synchronized with canonical `skills/` sources: 3094 matched, 0 drift.