alexanderandClaude Opus 5.5 8f47303605 Grade SARIF findings by score, then CWE, then level ...

A result's own security-severity score is banded like CVSS; without one,
the finding is graded by a hand-built CWE table; failing that, by its
SARIF level, one band lower than before. The scanners' levels said more
about the tool than about the risk: a container running as root came out
Critical and a hard-coded password Medium.

The summariser only reads security-severity off the rule, and Lynkeus
scores each result, so the runs are summarised here to keep that score.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-24 21:06:44 +02:00

..

commands

Let the project name and the manufacturer be supplied on the command line

2026-09-24 20:41:56 +02:00

template

Add toc and include all findings in the report

2026-09-24 20:33:00 +02:00

vendor

Allow generation of metrics.json simply by accessing the artifacts folder.

2026-09-21 21:30:32 +02:00

__init__.py

Fix accidentially pushed folder structure

2026-09-19 11:10:01 +02:00

__main__.py

Allow generation of metrics.json simply by accessing the artifacts folder.

2026-09-21 21:30:32 +02:00

context.py

Grade SARIF findings by score, then CWE, then level

2026-09-24 21:06:44 +02:00

cvss_utils.py

Allow generation of metrics.json simply by accessing the artifacts folder.

2026-09-21 21:30:32 +02:00

layout.py

Retitle the report and drop the report and artifact ids

2026-09-24 20:41:06 +02:00

metrics.py

Integrate metrics from metrics.json into the report pdf.

2026-09-21 21:47:29 +02:00

rendering.py

Let the project name and the manufacturer be supplied on the command line

2026-09-24 20:41:56 +02:00

sample.py

Initial commit. monorepo deps are copied in a dirty way to the vendor folder

2026-09-18 16:58:29 +02:00

severity.py

Grade SARIF findings by score, then CWE, then level

2026-09-24 21:06:44 +02:00

sources.py

Allow generation of metrics.json simply by accessing the artifacts folder.

2026-09-21 21:30:32 +02:00