@brokkai/slopcop 0.0.6 → 0.0.7
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/README.md +7 -7
- package/native/darwin_amd64/slopcop +0 -0
- package/native/darwin_arm64/slopcop +0 -0
- package/native/linux_amd64/slopcop +0 -0
- package/native/linux_arm64/slopcop +0 -0
- package/native/windows_amd64/slopcop.exe +0 -0
- package/native/windows_arm64/slopcop.exe +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -269,7 +269,7 @@ check outside your workspace.
|
|
|
269
269
|
The service answers structured data; the CLI renders it. `human` prints one
|
|
270
270
|
block per new finding, with an `ID:` line when the service names one, then a
|
|
271
271
|
summary line such as `1 new finding across 1 file(s); 72 already in the code |
|
|
272
|
-
Analysis complete`, and any omitted or
|
|
272
|
+
Analysis complete`, and any omitted new findings or
|
|
273
273
|
incomplete checks. `json` prints `status`, `baseCommit`, `summary`
|
|
274
274
|
(`newFindings` and `existingFindings` count the split), `findings` (each with
|
|
275
275
|
`new` and its `id`), `incomplete`, and `failure` when the analysis did not
|
|
@@ -292,12 +292,12 @@ interrupted check prints no report. Interrupted before it was sent, nothing
|
|
|
292
292
|
reached the service; after, a service that received it keeps running it, and
|
|
293
293
|
running the same check again picks up its result.
|
|
294
294
|
|
|
295
|
-
An inconclusive check
|
|
296
|
-
|
|
297
|
-
|
|
298
|
-
|
|
299
|
-
|
|
300
|
-
|
|
295
|
+
An inconclusive check, one that ran but could not prove there is nothing
|
|
296
|
+
more to find, never changes the exit code and is not named in any format.
|
|
297
|
+
Complete proof is rare in static analysis, typically at a library boundary,
|
|
298
|
+
so this is the norm rather than a gap. `summary.inconclusive` counts them in
|
|
299
|
+
`json`, as does `slopcop.inconclusive` in `sarif`. A check that timed out or
|
|
300
|
+
that Bifrost judged unreliable is incomplete and counts wherever it is.
|
|
301
301
|
|
|
302
302
|
The service applies `--fail-on` and sets the status; the exit code follows it.
|
|
303
303
|
The CLI always sends `--fail-on`, defaulting to `finding`: a check fails only
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|