The report (47 passages, no note) the linter writes for a forge with --format: a SARIF log that GitHub code scanning shows in the margin of the diff, on the file and line of each finding; a JUnit report that a GitLab merge request lists as failed tests with the message, the remediation and the page of each; or JSON, which also names the scope, the checks that ran and whether the global scope was degraded. Every form carries the same findings as the text output, and --output writes it to a file, the only file the linter ever writes.
Forge report
Properties3
- Application
- Concordance command line
- Domain
- Quality
- Status
- valid
3 declared keys. The rest of the file is free text.
See the neighbourhood map6 pages6Neighbourhood mapForge report
Neighbourhood map Forge report
Distance1 hop
33 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- FindingTermspecializes8
- RemediationTermspecializes3
- LinterTermspecializes8
- ScopeTermspecializes2
- CheckTermgeneralizes9
- Local checkTermgeneralizes2
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.