coverme-scanner 1.11.1 → 1.11.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.
|
@@ -296,3 +296,33 @@ Before finishing, verify:
|
|
|
296
296
|
3. **DREAD + Attack Chain** - Required for critical/high
|
|
297
297
|
4. **Run `coverme report`** - Opens HTML in browser
|
|
298
298
|
5. **Quality over quantity** - 10 good findings > 50 vague ones
|
|
299
|
+
|
|
300
|
+
---
|
|
301
|
+
|
|
302
|
+
## FINAL STEP - MANDATORY!
|
|
303
|
+
|
|
304
|
+
### Step 1: Validate JSON
|
|
305
|
+
|
|
306
|
+
After saving `.coverme/scan.json`, validate it:
|
|
307
|
+
|
|
308
|
+
```bash
|
|
309
|
+
python3 -m json.tool .coverme/scan.json > /dev/null && echo "JSON valid" || echo "JSON invalid - fix it!"
|
|
310
|
+
```
|
|
311
|
+
|
|
312
|
+
**If JSON is invalid, fix the syntax errors before proceeding!**
|
|
313
|
+
|
|
314
|
+
Common JSON errors:
|
|
315
|
+
- Missing `]` to close arrays (especially `attackChain`)
|
|
316
|
+
- Missing `}` to close objects
|
|
317
|
+
- Trailing commas before `]` or `}`
|
|
318
|
+
- Unescaped quotes in strings
|
|
319
|
+
|
|
320
|
+
### Step 2: Generate HTML Report
|
|
321
|
+
|
|
322
|
+
```bash
|
|
323
|
+
coverme report
|
|
324
|
+
```
|
|
325
|
+
|
|
326
|
+
**The scan is NOT complete until the HTML report opens in the browser!**
|
|
327
|
+
|
|
328
|
+
If `coverme report` fails with JSON error, fix the JSON first.
|