Skip to main content

EXTENSIONS

Selection
7 results
label:provenance

Signed Images

@dataverket/signed-images · v2026.11.10.1

Nine workflows composing @dataverket/ko, @dataverket/cosign, @dataverket/flux and @dataverket/crane. `@dataverket/ko-signed-images`: a signed build, every command of one Go module built into an image by ko and pushed, every image signed by digest with cosign using a key held in a vault, every signature verified. `@dataverket/ko-signed-manifests`: signed manifests, ko resolve renders them with every ko:// image built, pushed and pinned by digest, each image is signed, the rendered manifests are attested onto it as a custom predicate, and both are verified. `@dataverket/verified-manifests`: every image a rendered manifest file names verified against a public key, read-only, a gate before a deploy. `@dataverket/signed-release`: a directory of rendered manifests pushed as one OCI artifact with flux push artifact, tagged with the commit, with a release.json listing every image by digest from this run's resolution record, the artifact signed by digest, the rendered manifests attested onto it, both verified. `@dataverket/verify-release`: the gate, read-only, the artifact's tag pinned to its digest with crane, its signature and custom attestation verified against a public key, release.json read out of its layer, every image it lists verified by digest. `@dataverket/pinned-base-image`: an upstream base image resolved to its digest with crane, held in quarantine until that digest has been the tag's for minimumAgeDays, verified keyless against the publisher's identity, copied into our registry by digest, signed with our key and verified, the mirror record then feeding ko-signed-images through baseImageFrom. `@dataverket/promote-release`: verify-release as a nested workflow, then the channel tag such as current pointed at the verified digest with crane tag and read back, the digest it held before recorded for a rollback. `@dataverket/mirror-release-images`: verify-release, then every image the release lists copied by digest into another registry with its sha256-<hex> signature tag, and verified there. `@dataverket/verified-upstream-image`: read-only, an upstream image by tag, digest or both resolved to its digest with crane and its signature verified keyless against the certificate identity and OIDC issuer of its publisher; only when an attestationType is given, also its attestation of that type, where an attestation counts only when its subject is that digest and, when asked, its provenance names exactly the source repository and commit given; with attestationType empty, which the caller must say, a pass is about the signature alone; no vault, nothing written but records; it needs @dataverket/cosign 2026.11.10.1 or later. Each run fails unless all of what it was asked happened for all of the images. Every workflow refuses an input it does not have, so a mistyped name cannot switch a check off: from the command line by its input schema, from a step of another workflow by its first assertion.

upd Nov 1010 pullsA100/100

Session Suite

@vcjdeboer/session-suite · v2026.09.19.3

Agent + human guidance for the swamp session-* suite: how to record a live session, author a governed analysis (fill a frozen template's typed slots, validated), run it headless, and seal it — and where the R env flake, templates, and recorder clients live. Wire an R project to record its work with the writer init on-ramp.

upd Sep 1933 pullsA93/100

Session Record

@vcjdeboer/session-record · v2026.09.18.3

Never lose how a result was computed. A language-agnostic provenance ledger for interactive data-science sessions: append one immutable, content-checksummed record per executed cell/chunk — its code, value, figures, console output, warnings, packages, and even runtime-declared functions with their internal dependencies — from any client (R/RStudio, Python/Jupyter, targets, …). One append-only ledger, one record per cell, identical shape across languages: the foundation the rest of the session-* suite fills, seals, and replays. Capture the real computation as it happens, so a session can be audited, sealed (session-witness), or re-run later — not reconstructed from memory.

upd Sep 18417 pullsA93/100

Session Execute

@vcjdeboer/session-execute · v2026.09.18.3

The headless runtime of the session-* suite. Runs a filled analysis template — R/qmd in a pinned nix R env (`run`), a targets pipeline via a harvester (`run-targets`), or Python/ipynb via papermill in the locked conda/Docker env (`run-notebook`) — with the recorder armed or a swamp.returns contract verified. Also faithfully REPLAYS a captured session: `replay` re-runs recorded R against frozen tolerance rules (nix preferred, docker fallback), and the Python host-replay shim serves a captured session's host.* calls offline (or falls through to the live API in hybrid mode). Reproduce a governed run — or a foreign Claude Science session — deterministically.

upd Sep 1840 pullsA93/100

Session Ingest

@vcjdeboer/session-ingest · v2026.07.27.1

Lift your own Claude Science (operon) sessions out of the local operon-cli.db into open, replayable, sealable swamp records: a typed transcript, a turn->execution->artifact->env provenance graph, an immutable content-addressed byte corpus, the FULL ordered cell script, the CS skills the session used, its replayable host.* calls, a Tier-1 /private/tmp input freeze, a per-source external-data inventory, a presence-only credential manifest, and reproducible Docker + Nix environment locks — then `seal` an order-stable bundle-manifest (witness-digested). With @vcjdeboer/session-execute run-notebook + a host-replay shim, a captured session RE-RUNS outside the app. Reads a disposable scrubbed clone (secret tables dropped and never decrypted; explicit column allow-list; refuses a mid-run session), read-only, deterministic. Anti-lock-in data portability for your own local sessions.

upd Jul 2741 pullsA93/100

Session Witness

@vcjdeboer/session-witness · v2026.07.16.1

Prove a recorded data-science session hasn't been altered since you sealed it. The Master member of the session-* suite: a tamper-evident seal + authorship attestation, with no keypairs or infrastructure. `seal` chains the per-version content checksums of a session-record ledger (in sequence) into one sha256 session digest and attests its authors; `verify` recomputes the digest and reports whether a sealed session still matches. `seal_manifest` generalizes the primitive to ANY ordered {name, checksum} list — so a session-ingest bundle-manifest seals exactly the same way. Change one byte of any past record and the digest changes: the seal breaks, loudly. Ultralight integrity for governed, reproducible science — the trust layer under the whole suite.

upd Jul 1636 pullsB86/100

Sourced Kb

@stateless/sourced-kb · v2026.06.23.2

A domain-neutral, sourced, versioned knowledge base — the provenance-aware core generalised out of @stateless/llm-catalog. One uniform `entry` record (open `kind` + open `facets` + `claims` + `relations`, like @stateless/inventory), but with a provenance envelope (asOf, source, versionPins, supersededBy) on every volatile assertion, so it can hold external, decaying, contested knowledge honestly — a value without a date + source is not trustworthy here. Declarative lifecycle: `apply` materialises the declared entries (re-run = versioned trend), `update` folds in a public catalog without clobbering local truth, `prune` soft-retires undeclared entries, `contribute` sanitises selected entries into PR-ready public fragments. It knows no domain (no typed facets, no compute methods); a consuming catalog — LLM-ops, cloud-storage pricing — is an instance whose entries carry that domain's kinds and facets.

upd Jun 2386 pullsA93/100