ajtazer/heckit / skills/cve-hunting/target-recon
target-recon
VerifiedTarget discovery methodology for finding high-quality npm/PyPI/GitHub packages to audit for vulnerabilities, with evaluation criteria and search strategies.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.6 KB |
| references/parallel-scanning.md | markdown | 1.5 KB |
| references/search-queries.md | markdown | 2.4 KB |
references/parallel-scanning.md
View on GitHub# Parallel Target Scanning
## Batch Evaluation Methodology
When evaluating multiple targets, parallelize the process:
### Phase 1: Discovery (Parallel)
Run multiple search queries simultaneously:
```bash
# Run these in parallel
gh search repos "xml parser" --language javascript --stars 500..15000 --json name,stargazersCount,updatedAt
gh search repos "csv parse" --language javascript --stars 500..15000 --json name,stargazersCount,updatedAt
gh search repos "yaml" --language python --stars 500..10000 --json name,stargazersCount,updatedAt
```
### Phase 2: Dedup (Sequential)
Check each result against REGISTRY.md. Skip already-investigated packages.
### Phase 3: Quick Assessment (Parallel)
For each remaining candidate, quickly assess:
1. Last commit date (skip if > 6 months old)
2. Existing CVE count (skip if > 10)
3. SECURITY.md presence (bonus)
4. Download count (skip if < 100K weekly for npm)
### Phase 4: Deep Evaluation (Sequential)
For the top 5-10 candidates:
1. Clone repo
2. Count lines of code
3. Identify attack surface
4. Match to vulnerability skills
5. Write brief
6. Propose to Director
## Rate Limiting
- GitHub API: 30 search requests per minute (authenticated)
- npm API: generous limits for search
- grep.app: be reasonable, no rate limit documented
## Subagent Parallelization
When using Claude Code, spawn subagents for parallel evaluation:
- Each subagent evaluates one target
- Main agent collects results and deduplicates
- Final ranking by estimated CVE potential
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |