Skip to main content

Ci Verification

@webframp/ci-verificationv2026.11.12.1· Apache-2.0· 8d agoBEHAVIORSWORKFLOWS
01README

Pre-PR verification for webframp/swamp-extensions, as typed, versioned swamp data. Runs the checks CI runs against one commit, in a throwaway worktree at that commit, and records every result and its log keyed by the commit's tree hash. Builds an attestation from the recorded results and posts it as a git ref (refs/attestations//), never forced.

Quick Start

swamp extension pull @webframp/ci-verification

# Verify a commit of a swamp-extensions checkout. Each workflow step names
# the model type and the instance name ci-verification, so swamp creates
# that instance on the first run.
swamp workflow run @webframp/ci-verification-verify \
  --input repoPath=/path/to/swamp-extensions \
  --input commit=<sha> --input base=<base-sha>

# Build and post the attestation once reviews are done. A change to the
# trust root (ci-discover, check-reserved-names, this extension, CI
# workflows) needs an approval with decision "approve". To run methods
# before the workflow has run, create the instance first:
#   swamp model create @webframp/ci-verification ci-verification
swamp model method run ci-verification attest \
  --input repoPath=/path/to/swamp-extensions --input commit=<sha> \
  --input 'approvals:json=[{"gateId":"release-approval","decision":"approve"}]'
swamp model method run ci-verification post \
  --input repoPath=/path/to/swamp-extensions --input commit=<sha>

Methods

  • discover: which extensions the diff selects, from the repository's own scripts/ci-discover
  • check: check, lint, fmt:check, test and manifest fmt per extension, plus the repo-wide checks CI runs
  • quality: the registry quality rubric per extension
  • attest: the attestation for a tree, from recorded results
  • post: push the attestation as a git ref

Workflow

  • @webframp/ci-verification-verify: discover, check and quality in sequence
02Release Notes

2026.11.12.1

Added: Initial release. A model, @webframp/ci-verification, that runs the checks swamp-extensions CI runs against one commit and records every result and its log as swamp data, keyed by the commit's tree hash:

  • discover records which extensions and repo-wide checks the diff selects, using the commit's own scripts/ci-discover.
  • check runs each selected extension's check, lint, fmt:check, test and manifest fmt, plus the reserved data name scan, the import specifier greps and the tasks of each touched scripts/ tool.
  • quality runs swamp extension quality under CI's pass condition.
  • attest builds an attestation from the recorded results and refuses if any result is missing, failed, or stale, if a review failed or an approval's decision is not approve, or if the change touches the trust root (ci-discover, check-reserved-names, this extension, CI workflows) and no approval with decision approve was given.
  • post pushes the attestation to refs/attestations/<tree>/<timestamp>, never forced.

Every method runs in a throwaway worktree at the commit, with an allowlisted environment for child processes. A rerun reuses passed results and reruns failed ones.

Added: The @webframp/ci-verification-verify workflow, which runs discover, check and quality in sequence.

03Behaviors1
@webframp/ci-verificationv2026.11.12.1ci_verification.ts
fn discover(base: string)
Record which extensions and repo-wide checks the diff from base selects, using the commit's own scripts/ci-discover
ArgumentTypeDescription
basestringThe base the diff is taken against
fn check()
Run check, lint, fmt:check, test and manifest fmt for every selected extension, and the repo-wide checks, recording each result and its log
fn quality()
Run swamp extension quality for every selected extension under CI's pass condition, recording each result and its log
fn attest(reviews?: array, approvals?: array)
Build the attestation for a commit\'s tree from its recorded results; writes nothing unless every selected check passed for this selection and model version, and, when the change touches the trust root, an approval with decision "approve" is given
ArgumentTypeDescription
reviews?arrayReview verdicts, recorded as asserted by the caller
approvals?arrayApprovals, recorded as asserted by the caller; when the change touches the trust root, one must have decision "approve"
fn post(remote?: string)
Push a commit's attestation to refs/attestations/<tree>/<timestamp> on a remote, never forced
ArgumentTypeDescription
remote?stringThe git remote to push the ref to

Resources

selection(30d)— What the diff selects: extensions and repo-wide checks
check(30d)— One extension's check, lint, fmt:check, test and manifest fmt
quality(30d)— One extension's registry quality result
repocheck(30d)— One repo-wide check
attestation(infinite)— The attestation for a tree, built from recorded results
posted(infinite)— Where an attestation was posted

Files

log(text/plain)— The output behind one recorded result, capped at 256 KiB
04Workflows1
@webframp/ci-verification-verifydb8ee9fc-69b2-43d3-851e-fcd480b08c27

Verify a swamp-extensions commit before opening a pull request: discover which extensions the diff from base selects, then run each one's check, lint, fmt:check, test and manifest fmt with the repo-wide checks, then the registry quality rubric. Results and logs are stored as swamp data keyed by the commit's tree. Each job runs only when the one before it succeeded. The workflow never posts an attestation; run the model's attest and post methods when the change is ready to release.

discoverRecord which extensions and repo-wide checks the diff selects.
1.discover— Run the commit's own scripts/ci-discover against base.
checkRun each selected extension's tasks and the repo-wide checks.
1.check— Check, lint, fmt:check, test and manifest fmt per extension.
qualityScore each selected extension under CI's quality pass condition.
1.quality— swamp extension quality per extension.
05Stats
A
100 / 100
Downloads
3
Archive size
30.9 KB
  • Has README or module doc2/2earned
  • README has a code example1/1earned
  • README is substantive1/1earned
  • Most symbols documented1/1earned
  • No slow types (deprecated)1/1earned
  • Dependencies pass trust audit2/2earned
  • Docs keep secrets in a vault1/1earned
  • Has description1/1earned
  • Platform support declared (or universal)2/2earned
  • License2/2earned
  • Verified public repository2/2earned
06Platforms
07Labels