mk-vulnerability-scanner
Vulnerability analysis: OWASP Top 10, current threat landscape, supply chain security, attack surface mapping, risk prioritization. Use for security audits. NOT for STRIDE/CSO infra audits (mk:cso).
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 16
- Forks
- 3
01 前言 Front Matter
- name
- mk-vulnerability-scanner
- description
- Vulnerability analysis: OWASP Top 10, current threat landscape, supply chain security, attack surface mapping, risk prioritization. Use for security audits. NOT for STRIDE/CSO infra audits (mk:cso).
02 资源文件 1
- 参考文档references/scanning-methodology.md3.6 KB
03 SKILL.md 正文
<!-- Split for progressive disclosure (checklist #11, #14): 278 → ~55 lines -->
Vulnerability Scanner
Think like an attacker, defend like an expert.
When to Use
- Security audit of a project or module
- Before shipping code that handles auth, payments, or user data
- When asked to "scan for vulnerabilities", "security check", "audit security"
- When mk:cso delegates specific scanning tasks
Core Principles
| Principle | Application |
|---|---|
| Assume Breach | Design as if attacker already inside |
| Zero Trust | Never trust, always verify |
| Defense in Depth | Multiple layers, no single point |
| Least Privilege | Minimum required access only |
| Fail Secure | On error, deny access |
Process
- Map attack surface — entry points, data flows, trust boundaries, assets
- Load scanning methodology — read
references/scanning-methodology.md - Reconnaissance — understand technology stack, entry points, data flows
- Discovery — configuration review, dependency analysis, code pattern search
- Analysis — validate findings, eliminate false positives, score risks
- Report — each finding: What, Where, Why, Impact, How to fix
Threat Modeling Questions
Before scanning, ask: What are we protecting? Who would attack? How? What's the impact?
References
| Reference | When to load | Content |
|---|---|---|
| scanning-methodology.md | Step 2 — executing scan | OWASP Top 10, supply chain, code patterns, risk prioritization, reporting format |
Runtime Scripts
| Script | Purpose | Usage |
|---|---|---|
security-scan.py |
Security pattern scanning | .meowkit/envs/vulnerability-scanner/bin/python3 .codex/scripts/security-scan.py |
injection-audit.cjs |
Prompt injection detection | node .codex/scripts/injection-audit.cjs |
Gotchas
- False positives in test fixtures: Security scan flags intentionally insecure test data → Exclude test/fixtures/ and mocks/ from vulnerability scans
- Dependency confusion attacks missed: Scanner checks known CVEs but not package name typosquatting → Cross-reference package names against known typosquat databases
04 同仓库更多 Skills
mk-worktree
Manages git worktrees for parallel agent isolation: creates parallel/{name}-{timestamp} branches, merges with conflict detection. NOT for user feature branches (use git worktree directly).
mk-workflow-orchestrator
Auto-invoked 7-phase workflow for complex-feature intent; fasttrack mode for pre-approved specs. NOT for explicit single tasks (mk:cook), green-field builds (mk:autobuild), or simple fixes (mk:fix).
mk-web-to-markdown
Fetch a URL and return clean markdown, for arbitrary external pages (blog, RFC, GitHub issue, vendor doc) not covered by mk:docs-finder. Static-only by default; opt-in JS rendering available.
mk-vulnerability-scanner
Vulnerability analysis: OWASP Top 10, current threat landscape, supply chain security, attack surface mapping, risk prioritization. Use for security audits. NOT for STRIDE/CSO infra audits (mk:cso).
mk-vue
Vue 3 authoring/review: components, composables, reactivity, Pinia, Pinia Colada, file routing, forms. Composition API + script setup. Auto-activates on .vue files. Deep review: mk:vue-best-practices.
mk-vue-testing-best-practices
Vue 3 testing best-practices review: Vitest + Vue Test Utils for components, composables, Pinia, Router, async/Suspense, forms, a11y, plus Playwright E2E strategy. Advisory only.