Changelog

Windows support for pack operations, catalog search across all component kinds, and dependency security updates.

Windows

• New epack-core-windows-amd64.exe and epack-core-windows-arm64.exe release binaries carry the same SLSA Level 3 provenance as every other platform
• Windows covers pack operations: build, sign, verify, inspect, list, extract, merge, and diff. Collector and tool execution stays on macOS and Linux and fails closed on Windows
• Merge, filtered listing and extraction, and recursive result globbing handle Windows paths correctly

Catalog and utilities

• epack catalog search searches collectors, tools, remotes, and utilities with an optional --kind filter, and epack catalog refresh fetches the latest registry catalog with caching
• The new epack utility command installs, lists, and removes user-scoped utilities with Sigstore verification, tracked in a global utilities lock

Security

• Dependency updates for published advisories in sigstore-go and grpc-go
• Path validation rejects rooted paths on every platform

Lockfile verification metadata: every locked component records whether its signature was checked at lock time.

Lockfile

• Locked collectors, tools, and remotes gain a verification block recording the outcome of lock-time signature verification
• Components locked from GitHub releases record status: verified with a verified_at timestamp after their Sigstore bundles are checked against the pinned digests
• External binaries record status: skipped: they run from a local path and have no bundle to verify
• Lockfiles written by earlier versions carry no verification block, so consumers can tell verified and skipped entries apart from locks that predate verification recording

Committed-lockfile CI: strict locked installs, lockfile provenance reporting, and machine-readable errors.

CLI

• Added epack sync --locked: clean-machine CI install that fetches exactly the locked versions with full signature and digest verification, fails on any drift, and never rewrites the lockfile
• Added epack remote report-lock: report the current epack.lock.yaml to a remote without pushing a pack, for CI bootstrap and refresh flows
• Sync and frozen paths now validate range satisfaction: a pinned version outside its configured range fails with lock_config_mismatch instead of silently keeping the old pin
• Added EPACK_ERROR_FILE: failed commands append stable code=, exit=, and summary= lines for log-free CI error handling
• Runner context gains head_sha via EPACK_HEAD_SHA, the branch head on pull_request workflows where GITHUB_SHA is the merge commit

Remote Protocol

• Added the lock.report command and lock_report capability for lockfile provenance reports (conformance rule REM-090)
• push.prepare and push.finalize carry a structured lock_provenance envelope alongside the existing string build context, so releases record the exact lock that produced the pack

Errors

• New stable codes for frozen and locked failures: lock_config_mismatch, lock_stale, and lock_missing_pinned_artifact replace generic lockfile errors at the affected call sites

Richer artifact metadata for generated collector evidence.

Protocol

• Collector artifacts can carry display_name, description, and controls manifest metadata

Go SDK

• Added JSONArtifact, FileArtifact, and ArtifactMeta helpers for metadata-bearing collector artifacts

Collector file artifacts for binary evidence such as PDFs, screenshots, and archives.

Protocol

• Added EPACK_COLLECTOR_OUTPUT_DIR, a per-collector staging directory for raw file artifacts
• Collectors can emit file artifact entries whose bytes are packaged at the declared path
• Staged file paths reject traversal, absolute paths, symlinks, and non-regular files before packaging
• Staged bytes count toward artifact and pack budgets without counting against stdout limits

Go SDK

• Added componentsdk.Staging(ctx) for optional file-artifact staging helpers
• Added WriteStagedFile and StageFile helpers for buffered and streaming collector output

Security fixes for transitive dependencies.

Dependencies

• Bumped go-jose to v4.1.4 to fix a JWE decryption panic (GHSA-78h2-9frx-2jm8)
• Bumped sigstore/timestamp-authority to v2.0.6 for improper certificate validation in the verifier (GHSA-xm5m-wgh2-rrg3)
• Bumped go.opentelemetry.io/otel to v1.42.0 to fix a baggage-header allocation amplification (GHSA-mh2q-q3fh-2475)

Collection levels for graduated evidence gathering.

Protocol

• Reserved a top-level level config key with values trust, audit, internal; defaults to trust when absent
• Levels are cumulative: audit is a superset of trust; internal is a superset of audit
• Unknown values downgrade to trust with a stderr warning so collectors never gather more than was asked for
• Collectors honoring the field stamp collected_at_level on their top-level artifact for downstream interpretation

Go SDK

• Added componentsdk.Level with LevelTrust / LevelAudit / LevelInternal constants
• Added ctx.Level() reader and Level.AtLeast(other) comparator for gating field collection

Locktivity-managed credentials, portable hooks, build-context emission, and smoother GitHub Actions signing.

Managed Workflows

• Added top-level credential_sets for Locktivity-managed workflow integrations
• Collectors, tools, and remotes can request managed credentials by logical ref
• Locktivity remote auth docs now reflect access_token, device_code, and client_credentials

Runner UX

• Added epack hooks run for portable project hooks under .epack/hooks/
• Added epack context build to emit build metadata for runners
• Project scaffolding now keeps .epack/hooks/ tracked while ignoring other runtime state

CI/CD Signing

• epack sign now uses ambient GitHub Actions OIDC automatically when id-token: write is granted
• Other CI systems can continue to provide EPACK_OIDC_TOKEN explicitly

Profile and overlay support, multiple collector artifacts, and new top-level commands.

Profiles & Overlays

• Added profiles and overlays configuration sections in epack.yaml
• Support for registry-sourced profiles with version locking
• Profile/overlay digests tracked in manifest for reproducibility

Collector SDK

• Breaking: Emit() now accepts []CollectedArtifact for multiple artifacts per collection
• New CollectedArtifact struct with Schema and Path metadata
• Collectors can emit multiple artifacts in a single call

New Commands

• epack catalog search — unified search across collectors, tools, remotes, and utilities
• epack catalog refresh — update local catalog cache
• epack utility install/list/remove — manage global utilities

Remote Protocol

• Added runs.sync and auth.whoami feature capabilities
• Consistent sync behavior across collector, tool, and remote adapters

Bug Fixes

• Fixed offline verification mode to properly use embedded timestamps
• Fixed JSON output returning null instead of [] for empty arrays

Verification improvements and remote protocol enhancements.

Verification

• Improved error messages for attestation verification failures
• Added support for sigstore-js provenance bundles

Remote Protocol

• Added sidecar push support for parallel attestation uploads
• Improved push workflow reliability

Initial public release of the Evidence Pack specification and epack CLI.

Specification

• Evidence Pack format specification v1.0
• Manifest schema with SHA-256 digests for all artifacts
• Sigstore attestation bundle format
• Pack digest and manifest digest algorithms

CLI (epack-core)

• build — create packs from artifacts
• sign — keyless signing via Sigstore
• verify — integrity and signature verification
• inspect — view pack contents and metadata
• diff — compare two packs
• merge — combine multiple packs
• list — list artifacts in a pack
• extract — extract artifacts from a pack

CLI (Full)

• new — scaffold a new epack project
• init — initialize epack in existing directory
• collect — run collectors and build pack
• push / pull — remote registry operations
• lock / sync / install / update — dependency management
• collector / tool — plugin management

Go SDK

• pack — core pack types and operations
• pack/builder — fluent API for building packs
• pack/verify — verification with policy options
• sign — Sigstore signing integration