jumpring v0.1.2

jumpring v0.1.2

jumpring --version reported 0.1.0 regardless of which version was installed —
the number was a hardcoded literal that was never updated, so 0.1.1 shipped
reporting the wrong version. The CLI now reads its version from the package
manifest at runtime, so it cannot drift again.

No other changes. The keystore format, the cryptography, and the command surface
are unchanged; keystores are unaffected. Releases are published from CI with npm
Trusted Publishing (OIDC) and carry a signed provenance attestation, as in 0.1.1;
verify with npm audit signatures after install.

MIT licensed. See the README for the threat model.

jumpring v0.1.1

jumpring v0.1.1

No functional changes. The keystore format, the cryptography, and the command
surface are all unchanged; keystores written by 0.1.0 are unaffected.

• Provenance. Releases are now published from CI using npm Trusted Publishing
  (OIDC), so every published tarball carries a signed attestation binding it to
  this repository and the exact commit it was built from. No long-lived publish
  token exists. Verify with npm audit signatures after install, or on each
  package's npm page.
• Manifests link their source. All three packages now carry repository,
  homepage, and bugs fields.
• Documentation. Added guidance on pinning versions, building from source, and
  key hygiene for agent operators.

Known issue: jumpring --version reports 0.1.0 in this release regardless of
the installed version. It is fixed in 0.1.2, which reads the version from the
package manifest.

MIT licensed. See the README for the threat model.

jumpring v0.1.0

jumpring v0.1.0 — the first release.

A small, auditable command-line tool for encrypted key custody and EVM chain
operations. Generate a passphrase, encrypt a private key into a keystore, derive
its address, and sign or broadcast transactions with it.

• @jumpring/core — Argon2id + AES-256-GCM keystore, EFF diceware, masked
  passphrase prompt. Zero chain dependencies.
• @jumpring/evm — RPC, account derivation, and signing over a jumpring keystore.
• jumpring — the CLI: genphrase, genkey, address, confirm, and the evm
  subcommands (sign-tx, sign-typed, read, send).

MIT licensed. See the README for the threat model.