Workerbee / Evaluate

Turn release questions into repeatable checks.

Evaluate makes the scope of a check visible. Local repository and rule checks, bounded inventories, and constrained comparisons produce evidence that can be reviewed without turning unsupported checks into an all-clear.

Implemented foundationLocal/development tooling; hosted pilot planned

This website does not accept module uploads, credentials, or source code.

EVALUATE

Illustrative output shape

A result.
With its boundaries.

Scope
A selected snapshot
Evidence kind
Static / imported / executed
Unsupported checks
Reported as not_run

An illustration, not a live run or customer report.

Inputs

Start with a clear scope.

Permitted repository snapshots, project rules, and explicitly labeled evidence

Outputs

Leave with reviewable evidence.

Findings, bounded inventories, comparison results, and checks that were not run

Implemented foundation

What exists locally.

  • Repository and rule checks
  • Bounded dependency inventory and basic pattern checks
  • Bounded reconstruction comparisons
  • Separate labels for static, imported, and executed evidence

Scope and limits

What this does not establish.

  • Gitleaks, OSV, and Semgrep wrappers currently report not_run
  • No claim of active scanner coverage
  • Reconstruction experiments are constrained measurements
  • No general penetration test, semantic analysis, or effectiveness guarantee

What we are building toward

The next step
needs its own evidence.

Expand evaluators carefully, with explicit execution evidence, coverage boundaries, and separate hosted acceptance.

Shared Evidence supports this work; formats and workflows are still being brought together.

See the Evidence foundation

Register module interest

Follow Evaluate.

The shared form will visibly preselect this module. You can change the selection.

Join early access