coverme-scanner 1.11.2 → 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.
|
@@ -301,15 +301,28 @@ Before finishing, verify:
|
|
|
301
301
|
|
|
302
302
|
## FINAL STEP - MANDATORY!
|
|
303
303
|
|
|
304
|
-
|
|
304
|
+
### Step 1: Validate JSON
|
|
305
|
+
|
|
306
|
+
After saving `.coverme/scan.json`, validate it:
|
|
305
307
|
|
|
306
308
|
```bash
|
|
307
|
-
coverme
|
|
309
|
+
python3 -m json.tool .coverme/scan.json > /dev/null && echo "JSON valid" || echo "JSON invalid - fix it!"
|
|
308
310
|
```
|
|
309
311
|
|
|
310
|
-
**
|
|
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
|
|
311
321
|
|
|
312
|
-
If `coverme report` fails, generate HTML manually:
|
|
313
322
|
```bash
|
|
314
|
-
|
|
323
|
+
coverme report
|
|
315
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.
|