[bayasdev]

From an audit of 1.0.1.

• reseal opens the value the sealer returned with the opener's current key and compares it with the original. Reading the key id on that value was still trusting a claim: a sealer of the caller's own could relabel its output, seal for another context, or seal another value.
• The publish workflow has three jobs with one permission each. The job that runs the toolchain can't publish or write to the repository; the job with the OIDC permission publishes the tarball the first one packed, with --ignore-scripts, and runs none of the project's code. The tag must be a commit of main.
• Every action in both workflows is pinned to a commit SHA, and checkouts don't keep their credentials.
• The README notes that a public key and a secret key can't be told apart, and the 1.0.1 changelog entry no longer overstates what opens on big-endian machines.

Releases 1.0.2.