Add independently verifiable provenance for self-update bundles

Open
#230 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
34/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, typescript
Domain
devops, security

Research direction

Start by reading the existing checksum and self-update flow, then inspect the release workflow and SECURITY.md. Define the provenance trust model and compatibility behavior before implementing production and verification; use dummy releases to check valid, missing, mismatched and invalid provenance. Done means the updater verifies artifact identity, repository and version before activation, and the wiki documents verification and recovery.

Written by the indexing model from the issue text.

Description

enhancement

What to build

Extend the existing bundle checksum flow with a documented provenance/signature policy that the updater verifies before importing or activating application code.

Context

Defense-in-depth follow-up to #172 and #118. Existing checksums verify matching release bytes; publisher compromise was not observed. Define the added trust guarantee before implementation.

This follows the November 17 source audit. Treat it as a hardening/validation task, not a confirmed exploit report. Detailed audit evidence and validation limitations remain in the local audit report; report any confirmed vulnerability privately under SECURITY.md.

Acceptance criteria

  • Document the trust model, signing/provenance authority and threat boundary added beyond a checksum stored beside a bundle.
  • Produce provenance/signatures in the release workflow and verify artifact identity, repository and version before activation.
  • Define key/identity rotation, failure handling and compatibility for older releases without silent verification bypass.
  • Test valid provenance and rejected missing, mismatched or invalid provenance using dummy releases.
  • Update the wiki with update-verification behavior and compatibility/recovery guidance.

Blocked by

None (can start independently). Coordinate with related issues without expanding their scope.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
13h 12m
Merged PRs (30d)
57

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Isopod-Project/Isopod

All issues in Isopod-Project/Isopod

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.