Skip to content

Releases: usesecure/secure-bench

Secure Bench v0.2.1

Choose a tag to compare

@danielcadev danielcadev released this 17 Jul 13:58
v0.2.1
e6f1de0

Secure Bench 0.2.1 stabilizes prospective historical-integrity verification.

Highlights:

  • Anchors the immutable Phase 0-11 baseline to commit 86aa6f4.
  • Protects 2,403 files across 14 closed roots plus 26 individually protected files.
  • Keeps mutable governance and prospective namespaces outside the frozen historical boundary.
  • Fails closed on mutation, deletion, conflicting additions, symlink substitution, malformed manifests, overlap, and path traversal.
  • Adds Phase 12 to the six-workspace GitHub Actions matrix.

Secure Bench v0.2.0, its signed tag, published artifacts, Evidence Contract v2, taxonomy 1.0.0, and the official Phase 10 result remain unchanged.

No scanner result, ranking, production-readiness assessment, superiority claim, or complete-coverage guarantee is included.

Secure Bench v0.2.0

Choose a tag to compare

@danielcadev danielcadev released this 17 Jul 13:20
v0.2.0
359c723

Secure Bench 0.2.0 establishes the repaired prospective methodology for future neutral scanner evaluations.

Highlights:

  • Evidence Contract v2 is authoritative and malformed or conflicting projections fail closed.
  • Taxonomy expectations derive from the frozen Secure Bench taxonomy 1.0.0.
  • Direct flows use connected concrete values and paired controls protect the same value with terminating, sink-dominating barriers.
  • Process-status adjudication remains separate from adapter matching.
  • Includes a disclosed 28-pair public regression corpus and 19 Evidence Contract v2 conformance vectors.

Historical Phase 0-11 payloads and the official Phase 10 result remain unchanged.

This release defines benchmark methodology and public conformance material. It is not a scanner result, ranking, production-readiness assessment, superiority claim, or complete-coverage guarantee.