control-plane: rescan

What happened, why, and what came out of it. Written by the harness from its own records; a person decides what to do with it. The same story opens the run's folder as README.md; the example's write-up is on its example page.

repository control-planelanguage gomode rescanhead 147f74f4edc2started 2026-09-13T20:43:59+00:00harness 0.1.0run 558e6e085fe1
This run has not reached the review packet yet; the last stage that wrote was self-verification.

Who, what, why, where, when

WhoThe AI Test Harness 0.1.0 did the work without a person in the loop. A person decides the result; nothing in this run has been merged.
WhatA scheduled scan of control-plane at 147f74f4edc2, no change under review. 14 of 251 packages carry known vulnerabilities. Tests for github.com/getkin/kin-openapi v0.139.0, github.com/gomarkdown/markdown v0.0.0-20240328165702-4d01890c35c0, github.com/jackc/pgx/v5 v5.8.0, github.com/klauspost/compress v1.18.5, github.com/labstack/echo/v4 v4.15.1, github.com/nats-io/nats-server/v2 v2.12.5, github.com/yuin/goldmark v1.4.13, go.opentelemetry.io/otel v1.43.0, golang.org/x/crypto v0.51.0, golang.org/x/mod v0.35.0, golang.org/x/net v0.53.0, golang.org/x/text v0.37.0, google.golang.org/grpc v1.81.0, oras.land/oras-go/v2 v2.6.0.
WhyThe risk score decides the budget; the two strongest reasons per package: github.com/getkin/kin-openapi (score 70, budget full): reachable from first-party code; 8 known vulnerabilities for this version. github.com/gomarkdown/markdown (score 55, budget snapshot): reachability unknown, treated as reachable; 4 known vulnerabilities for this version. github.com/jackc/pgx/v5 (score 55, budget snapshot): reachability unknown, treated as reachable; 6 known vulnerabilities for this version. github.com/klauspost/compress (score 45, budget snapshot): reachability unknown, treated as reachable; 1 known vulnerability for this version. github.com/labstack/echo/v4 (score 55, budget snapshot): reachability unknown, treated as reachable; 2 known vulnerabilities for this version. github.com/nats-io/nats-server/v2 (score 45, budget reduced): 22 known vulnerabilities for this version; at least one advisory carries a severity rating. github.com/yuin/goldmark (score 45, budget snapshot): reachability unknown, treated as reachable; 1 known vulnerability for this version. go.opentelemetry.io/otel (score 45, budget snapshot): reachability unknown, treated as reachable; 1 known vulnerability for this version. golang.org/x/crypto (score 65, budget full): reachability unknown, treated as reachable; 30 known vulnerabilities for this version. golang.org/x/mod (score 45, budget snapshot): reachability unknown, treated as reachable; 2 known vulnerabilities for this version. golang.org/x/net (score 55, budget snapshot): reachability unknown, treated as reachable; 8 known vulnerabilities for this version. golang.org/x/text (score 45, budget snapshot): reachability unknown, treated as reachable; 1 known vulnerability for this version. google.golang.org/grpc (score 55, budget snapshot): reachability unknown, treated as reachable; 5 known vulnerabilities for this version. oras.land/oras-go/v2 (score 55, budget snapshot): reachability unknown, treated as reachable; 10 known vulnerabilities for this version.
WhereThe run's own files are in this folder.
WhenStarted 2026-09-13 20:43:59 UTC. The last stage to write was analysis at 2026-09-13 20:47:30 UTC.

Decisions the harness made

Actions it took

Actions it did not take, by design

How it happened, stage by stage

What each stage read, did and wrote, with the file behind every number.

  1. Self-verificationstage 0

    Read

    the harness's own code and the failure register

    Did

    • 19 register checks, all passed; sandbox probe skipped; model probe skipped.

    Wrote

    selfcheck/selfcheck.json

  2. Intakestage 1

    Read

    the repository at base and head, its dependency manifest

    Did

    • Resolved 250 packages at head and 250 at base with ; looked every version up in OSV: 14 with advisories at head; 0 changed; work list of 251 rows.

    Wrote

    intake/worklist.json · intake/graph.new.json · intake/sbom.new.cdx.json · intake/vulns.json

  3. Analysisstage 2

    Read

    the work list; package source, advisories, the application's call sites

    Did

    • 14 package(s) analyzed: github.com/getkin/kin-openapi score 70, budget full, 8 advisories, 0 breaking changes; github.com/gomarkdown/markdown score 55, budget snapshot, 4 advisories, 0 breaking changes; github.com/jackc/pgx/v5 score 55, budget snapshot, 6 advisories, 0 breaking changes; github.com/klauspost/compress score 45, budget snapshot, 1 advisories, 0 breaking changes; github.com/labstack/echo/v4 score 55, budget snapshot, 2 advisories, 0 breaking changes; github.com/nats-io/nats-server/v2 score 45, budget reduced, 22 advisories, 0 breaking changes; github.com/yuin/goldmark score 45, budget snapshot, 1 advisories, 0 breaking changes; go.opentelemetry.io/otel score 45, budget snapshot, 1 advisories, 0 breaking changes; golang.org/x/crypto score 65, budget full, 30 advisories, 0 breaking changes; golang.org/x/mod score 45, budget snapshot, 2 advisories, 0 breaking changes; golang.org/x/net score 55, budget snapshot, 8 advisories, 0 breaking changes; golang.org/x/text score 45, budget snapshot, 1 advisories, 0 breaking changes; google.golang.org/grpc score 55, budget snapshot, 5 advisories, 0 breaking changes; oras.land/oras-go/v2 score 55, budget snapshot, 10 advisories, 0 breaking changes.

    Wrote

    analyze/github.com/getkin/kin-openapi/facts.json · analyze/github.com/gomarkdown/markdown/facts.json · analyze/github.com/jackc/pgx/v5/facts.json · analyze/github.com/klauspost/compress/facts.json · analyze/github.com/labstack/echo/v4/facts.json · analyze/github.com/nats-io/nats-server/v2/facts.json · analyze/github.com/yuin/goldmark/facts.json · analyze/go.opentelemetry.io/otel/facts.json · analyze/golang.org/x/crypto/facts.json · analyze/golang.org/x/mod/facts.json · analyze/golang.org/x/net/facts.json · analyze/golang.org/x/text/facts.json · analyze/google.golang.org/grpc/facts.json · analyze/oras.land/oras-go/v2/facts.json

  4. Generationstage 3

    Read

    the fact bundle per package; the model; the sealed sandbox for baseline runs

    Did

    • did not run in this run.

    Wrote

    nothing

  5. Validation executionstage 4

    Read

    the candidate tests; the environments at head, base or the fixed candidate

    Did

    • did not run in this run.

    Wrote

    nothing

  6. Triagestage 5

    Read

    every verdict and finding from stage 4

    Did

    • did not run in this run.

    Wrote

    nothing

  7. Packetstage 6

    Read

    triage, the tests, the advisories

    Did

    • did not run in this run.

    Wrote

    nothing

  8. Attestationstage attest

    Read

    the manifest, the tests, the results; UDLM's chain code

    Did

    • did not run in this run.

    Wrote

    nothing

  9. Assessmentstage assess

    Read

    every record the run wrote, against the blueprint's goals

    Did

    • did not run in this run.

    Wrote

    nothing

  10. Test pull requeststage propose

    Read

    the packet and the records

    Did

    • did not run in this run.

    Wrote

    nothing

  11. Feedbackstage 7

    Read

    the pull request as a person decided it

    Did

    • did not run in this run.

    Wrote

    nothing

What is in this folder, and who it is for

What is in this folder, and who it is for

Every file exists for a reader or a tool named here. The plain-English files come first; the machine files stay because they are the proof and the replay.

Everyone

  • README.md: The story of this run: who, what, why, where, when, the outcome, the decisions and the actions.

Reviewers (the developer or team that owns the change)

Product Security

Supply Chain Security and auditors

  • run.json: What was run, with which tool versions, on which repository by name.
  • selfcheck/selfcheck.json: Stage 0: every failure-register check and the sandbox and model probes, before any evidence was produced.
  • intake/sbom.new.cdx.json: The software bill of materials at head, CycloneDX.

The person who ran the harness

Tools (kept for replay and proof; not meant to be read)