CyberSecurityUPandClaude Opus 5 d334946915 bench: refresh the TypeSafe benchmark — 13/13 coverage, data-type-aware severity ...

Current-build run against the 13-scenario target with TypeSafe on: every seeded
class confirmed with a live receipt, chained beyond the set into full admin
takeover, GraphQL authz bypass, a config secret leak and an authenticated RCE.
The credential-dump BOLA holds Critical because severity is graded on the kind
of data exposed, not the class. report.html + run artifacts + README refreshed;
no secrets committed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-20 14:06:39 -03:00

..

app

bench: refresh the TypeSafe benchmark — 13/13 coverage, data-type-aware severity

2026-09-20 14:06:39 -03:00

crates/harness

bench: refresh the TypeSafe benchmark — 13/13 coverage, data-type-aware severity

2026-09-20 14:06:39 -03:00

templates

release: v4.1.0 — assurance layer, TypeSafe, hardening + benchmark

2026-09-20 12:25:23 -03:00

.gitignore

chore: remove test artifacts, ignore scan debris (#35)

2026-07-31 15:39:00 -03:00

Cargo.lock

release: v4.1.0 — assurance layer, TypeSafe, hardening + benchmark

2026-09-20 12:25:23 -03:00

Cargo.toml

release: v4.1.0 — assurance layer, TypeSafe, hardening + benchmark

2026-09-20 12:25:23 -03:00

creds.example.yaml

docs: full creds.yaml reference (web/multi-role/ssh/windows/cloud) in TUTORIAL + example file

2026-07-02 08:44:00 -03:00