Hanzo Dev
925e692b8b
Two real bugs: - npx @hanzo/helper broke when the kms bin was added — a package with TWO bins can't be run by 'npx <pkg>' (could not determine executable). Reverted helper to its single 'hanzo' bin; kms stays as 'hanzo kms' AND as its own package. - version.ts was hardcoded '1.0.0' — 'hanzo --version' always lied. Now injected from package.json at build (tsup define __HANZO_VERSION__), one source of truth. - packages/kms: new standalone @hanzo/kms (single 'kms' bin) that re-runs the helper's kms CLI via the new ./kms-cli export. npm i -g @hanzo/kms → 'kms'. - exports: add ./kms-cli so the standalone package imports it cleanly. Published: @hanzo/helper@1.0.5, @hanzo/kms@1.0.5, @luxfi/@zenlm/@zooai/helper@1.0.5.
777 B
777 B
@hanzo/kms
Standalone
kmsCLI — sign in with IAM and pull environment secrets for local dev.
Same engine and token store as @hanzo/helper
(so kms and hanzo kms are interchangeable), packaged as its own kms command.
npm i -g @hanzo/kms # or: npx @hanzo/kms login
kms login # IAM device login (shared with `hanzo login`)
kms pull --env devnet # write .env for local dev
kms list --env devnet # secret names only
Environments: devnet (default), testnet, mainnet, production. Your org
comes from your login (--org to override). Secrets are read from KMS over the
canonical /v1/kms/orgs/{org}/secrets API; KMS gates access per env.
License
Apache-2.0