Package integrity

stackpkg

Know exactly what you install

HS / 01
stackpkg
Package integrityExact commit and content-hash pins
Source toolkit

Purpose, with substance.

stackpkg records where a package came from and which exact content was approved. A reproducible lockfile, optional signature verification, build adapters, a hash-chained audit trail, and a software bill of materials make source-based installation easier to inspect.

  • Exact commit and content-hash pins
  • Explicit build-script approval
  • Optional Ed25519 signatures
  • Audit verification and SBOM export
A closer look

From input
to useful outcome.

Who it serves

Builders who want inspectable source-based installation

What goes in

A repository or local source, pinned revision, approved content

What comes out

A lockfile, installation record, integrity result, and SBOM

01

Register the source

Identify the repository and the exact content to install.

02

Check the identity

Pin the commit and deterministic hash; verify a signature when required.

03

Approve the effect

Run build scripts only after explicit approval for that exact content.

04

Retain the evidence

Re-check installed content and export the audit or bill of materials.

Current scope & availability

Know where the project stands.

Build scripts execute upstream code when approved. The audit is tamper-evident, not tamper-proof; this is not a guarantee that an upstream package is safe.

Related by purpose

A useful place
in a bigger picture.

These assets share a workflow or engineering concern. Explore their individual scope before planning a connection.

Something worth building?

Let’s give it the care, clarity, and craftsmanship it deserves.

Tell us what you have in mind

Find your next possibility.

Search the collection · Esc to close · Ctrl / ⌘ K to open

Explore this project