Skip to content

feat: add SecurityEval reporting and CodeGuard 1.4.0 results - #137

Open
thomas-bartlett wants to merge 1 commit into
mainfrom
feat/securityeval-reporting
Open

thomas-bartlett wants to merge 1 commit into
mainfrom
feat/securityeval-reporting

Conversation

@thomas-bartlett

Copy link
Copy Markdown
Contributor

Add the CodeGuard 1.4.0 SecurityEval results and an exporter for future runs.

Related to #86 and #130.

The exporter turns validated Inspect logs into a results page, three charts, and summary and sample CSVs. Findings use shared cases, epochs stay separate, and costs use complete recorded costs or estimates from supplied token prices. Only allowlisted public fields are exported. Reporting dependencies are included in evaluation CI.

Validation:

  • 439 tests passed.
  • Strict MkDocs build passed.
  • All 726 published sample rows and derived totals were checked against the original six logs.
  • The report was regenerated, with matching CSVs and charts.

Export validated Inspect logs into generated tables, three charts, and public CSVs. Support per-epoch comparisons and consistent cost estimates while exporting only allowlisted fields.

Include the CodeGuard 1.4.0 results, export documentation, reporting tests, and the plotting dependency group in evaluation CI.
@thomas-bartlett thomas-bartlett self-assigned this Oct 9, 2026
@thomas-bartlett thomas-bartlett added the documentation Improvements or additions to documentation label Oct 9, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants