Skip to main content
Some SDK assets change faster than releases do. Framework signature packs are the main one: new agent frameworks appear, existing ones change their call shapes, and waiting for a wheel release to recognise them would make hexr analyze stale by design. hexr update fetches those assets, and verifies them before installing.

​
Why the verification matters more than the update

A signature pack tells hexr build and hexr analyze what an agent framework looks like. Anything that can rewrite those files can change what Hexr recognises — and quietly stop recognising something is the failure you would never notice. So the feed is signed with Sigstore keyless signing, and hexr update verifies:
  • the signature chains to Sigstore’s trust root
  • the certificate identity matches the expected workflow that publishes it
  • the Rekor transparency log entry exists
If any of those fail, nothing is written. A pack that cannot prove where it came from does not get installed.
Verification requires the ops extra:
It is kept out of the default install so agent pods do not carry sigstore, cryptography and their dependencies. Install it on developer, CI and operator machines — the ones that actually run this command.

​
Commands

​
command
Fetch and verify the current signature pack from the signed feed, then install it into the SDK’s pack directory.

​
Checking what you have

The manifest records which pack version classified each call site, so a surprising classification can be traced to the pack that produced it.

​
When it fails

The installed sigstore is too old for Sigstore’s current trust root. Upgrade:
Versions below 4.5.0 cannot verify against the current root and exit non-zero on every attempt.
The ops extra is not installed. See the warning above — this is deliberate, not a packaging bug.
Do not work around this. It means the pack you were served does not match what the publishing workflow signed. Re-run once in case of a partial download; if it persists, report it rather than bypassing it.