coverme-security-scanner 3.7.1 → 3.7.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/commands/coverme.md +9 -36
- package/package.json +1 -1
package/commands/coverme.md
CHANGED
|
@@ -1,48 +1,21 @@
|
|
|
1
|
-
# Security Assessment
|
|
1
|
+
# Security Assessment
|
|
2
2
|
|
|
3
|
-
Run a
|
|
3
|
+
Run a security scan and generate a PDF report. Execute automatically without asking questions.
|
|
4
4
|
|
|
5
5
|
## Step 1: Setup
|
|
6
|
-
Run this command using Bash:
|
|
7
6
|
```bash
|
|
8
7
|
mkdir -p .coverme
|
|
9
8
|
```
|
|
10
9
|
|
|
11
|
-
## Step 2:
|
|
12
|
-
|
|
10
|
+
## Step 2: Run Security Scan
|
|
11
|
+
Use ONE Task agent with subagent_type="general-purpose" to perform the full security assessment:
|
|
13
12
|
|
|
14
|
-
|
|
15
|
-
Analyze this codebase architecture and security posture. Identify tech stack, components, trust boundaries. Write findings to .coverme/partial-01-executive.json as valid JSON with fields: project (string), date (YYYY-MM-DD), executiveSummary (string), architecture (object with overview string, components array of {name, technology, description}, trustBoundaries array of {id, boundary, trustLevel, description}), topPriorities array of {finding, severity, action}.
|
|
13
|
+
prompt: "Perform a comprehensive security assessment of this codebase. Analyze: 1) Architecture and tech stack 2) API endpoints and attack surface 3) Security vulnerabilities (secrets, injection, XSS, auth issues) 4) Infrastructure (Docker, CI/CD, dependencies). When done, use the Write tool to create .coverme/scan.json with this structure: {\"project\":\"<name>\",\"date\":\"2026-02-19\",\"executiveSummary\":\"<summary>\",\"summary\":{\"critical\":0,\"high\":0,\"medium\":0,\"low\":0,\"total\":0},\"overallRiskLevel\":\"low|medium|high|critical\",\"findings\":[{\"id\":\"VULN-01\",\"title\":\"\",\"severity\":\"critical|high|medium|low\",\"file\":\"\",\"line\":0,\"issue\":\"\",\"why\":\"\",\"fix\":\"\",\"cwe\":\"\"}],\"architecture\":{\"overview\":\"\",\"components\":[]},\"positiveObservations\":[{\"title\":\"\",\"description\":\"\"}]}"
|
|
16
14
|
|
|
17
|
-
|
|
18
|
-
|
|
15
|
+
## Step 3: Wait for agent to complete
|
|
16
|
+
Use AgentOutputTool to wait for the agent.
|
|
19
17
|
|
|
20
|
-
|
|
21
|
-
Hunt for security vulnerabilities: hardcoded secrets, SQL injection, XSS, command injection, auth bypass. Include actual code snippets. Write to .coverme/partial-03-vulns.json as valid JSON with findings array containing: id, title, severity (critical/high/medium/low/info), file, line, issue, why, fix, cwe, codeEvidence array of {file, startLine, endLine, code, annotation}, proofOfConcept.
|
|
22
|
-
|
|
23
|
-
**Agent 4 - Attack Chains:**
|
|
24
|
-
Identify how vulnerabilities combine for greater impact. Map attack scenarios. Write to .coverme/partial-04-chains.json as valid JSON with: attackChains array of {id, name, description, likelihood, impact, steps array of {order, findingId, action, outcome}, mitigationStrategy}, riskMatrix array of {category, currentRisk, residualRisk, trend}.
|
|
25
|
-
|
|
26
|
-
**Agent 5 - Business Logic:**
|
|
27
|
-
Find business logic flaws: race conditions, workflow bypass, privilege escalation. Write to .coverme/partial-05-business.json as valid JSON with: findings array, threatModel array of {id, severity, dread, status, finding}.
|
|
28
|
-
|
|
29
|
-
**Agent 6 - Infrastructure:**
|
|
30
|
-
Check Docker, K8s, CI/CD, secrets management, dependencies. Write to .coverme/partial-06-infra.json as valid JSON with: findings array, qualityReview object with deadCode/dryViolations/deprecated arrays.
|
|
31
|
-
|
|
32
|
-
**Agent 7 - Compliance:**
|
|
33
|
-
Map findings to SOC2, PCI-DSS, GDPR. Identify positive practices. Write to .coverme/partial-07-compliance.json as valid JSON with: complianceMapping array of {framework, controls array}, remediation object with p0/p1/p2/p3 arrays of {action, finding, owner}, positiveObservations array of {title, description}, privacyAnalysis array.
|
|
34
|
-
|
|
35
|
-
## Step 3: Wait for All Agents
|
|
36
|
-
After launching all 7 agents, wait for them to complete using AgentOutputTool.
|
|
37
|
-
|
|
38
|
-
## Step 4: Generate Report
|
|
39
|
-
After all agents complete, run this command using Bash:
|
|
18
|
+
## Step 4: Generate PDF
|
|
40
19
|
```bash
|
|
41
|
-
coverme
|
|
20
|
+
coverme .coverme/scan.json security-report.pdf && open security-report.pdf
|
|
42
21
|
```
|
|
43
|
-
|
|
44
|
-
## IMPORTANT INSTRUCTIONS
|
|
45
|
-
- Execute ALL steps automatically - do not ask for confirmation
|
|
46
|
-
- Launch all 7 agents in PARALLEL (single message with 7 Task tool calls)
|
|
47
|
-
- Wait for ALL agents to complete before running the final command
|
|
48
|
-
- The PDF will open automatically when done
|