What the CLI does
The CLI can enroll a service, encrypt files locally before upload, create shares, download encrypted parts, and decrypt locally after download using service configuration kept outside browser code.
Automation
CLI and service API automation
ZipPigeon automation is designed for backends and operators that need encrypted upload, sharing, and download workflows without putting secrets in browser code.
Signed service requests
Service API calls use Ed25519 request signatures over method, path, timestamp, nonce, body hash, and service account ID. Replay protection and timestamp tolerance are part of the request model.
Token and scope boundaries
Service tokens are scoped for upload, share, and download actions. Token secrets are shown once, should live in a backend secret manager or local shell environment, and can be revoked.
Current package distribution
The CLI is not published to npm yet. The versioned package is served from the public download endpoint at https://www.zippigeon.com/downloads/zippigeon-cli-0.1.0.tgz.
Frequently asked questions
Can the CLI encrypt before upload?
Yes. The local CLI workflow encrypts before upload and decrypts after download, keeping service key bundles and passphrases outside browser code.
Should service tokens be used in frontend JavaScript?
No. Service tokens, key bundles, and passphrases belong in backend secret managers or local operator environments, not public browser code.
Send the file. Keep control of the link.
Use ZipPigeon when a file needs to reach the right person without becoming another attachment or shared folder to clean up later.
Open signed-in sender