certmate-cli
The CertMate SSL certificate
lifecycle from your terminal — built on certmate-sdk.
pip install certmate-cli # or, on macOS/Linux: brew install fabriziosalmi/certmate/certmate-cli
export CERTMATE_URL=http://localhost:8000
export CERTMATE_TOKEN=...
certmate cert create app.example.com --dns cloudflare --wait
certmate cert ls
certmate cert info app.example.com
certmate cert renew app.example.com --force
certmate cert create app.example.com --dns cloudflare --dry-run
certmate cert create app.example.com --name internal.example.com --dns cloudflare
certmate audit verify
--name names a second certificate for a domain apart from it: the certificate
is issued for app.example.com, and every later command takes
internal.example.com. The server must be on API contract 2.61 or later; an
older one would ignore the name, so the CLI asks first and refuses, and
--dry-run says whether the server takes it.
Pulling certificates onto a host
cert download fetches one file at a time, so a target server can pull
exactly what it deploys instead of the certificate manager pushing to it:
certmate cert download app.example.com --file fullchain -o /etc/ssl/certs/app.pem
certmate cert download app.example.com --file privkey -o /etc/ssl/private/app.key
Files are created 0600, with the mode set at creation rather than after the write, so the key is never briefly world-readable.
This is worth preferring over pushing when the manager would otherwise need
credentials on every target host. Give each host an API key scoped to its own
domain and run the pull on a timer: the host needs no inbound access, and the
manager holds no credentials for it. cert, chain and fullchain are
readable by a viewer-role key; privkey, combined and pfx need operator.
--file privkey --key-format pkcs1 serves the legacy
BEGIN RSA PRIVATE KEY form for stacks that reject certbot's PKCS#8.
--bundle zip or --bundle json fetch the whole certificate instead, and
-o - writes to stdout.
Connection comes from --url/--token or CERTMATE_URL/CERTMATE_TOKEN.
Prefer the CERTMATE_TOKEN environment variable over --token: command-line
arguments are visible to other local processes (ps) and shell history.
Metadata
Release files for certmate-cli 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| certmate_cli-0.1.6.tar.gz | 10.6 kB | With provenance | Details for certmate_cli-0.1.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| certmate_cli-0.1.6-py3-none-any.whl | Python 3 | none | any | Details for certmate_cli-0.1.6-py3-none-any.whl |
Total release size: 21.0 kB
Release files / certmate_cli-0.1.6.tar.gz
| Download URL | certmate_cli-0.1.6.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f29ad79eb013527346e9fcf0b7a729fdb4f239a244a8d72867d2dd3ea070646e
|
|
BLAKE2b-256 checksum How to use checksums |
75b8dd449afbdf1be5606f3c880ed0197d1b7bb7181b5aaf53d97751c03e8b30
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.
Transparency logRelease files / certmate_cli-0.1.6-py3-none-any.whl
| Download URL | certmate_cli-0.1.6-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26d4bfbfce68e60db221c1c56386f735d17de87cc2429ff5c8fa67a3911f6cda
|
|
BLAKE2b-256 checksum How to use checksums |
322d5164de9fce76ff29d443294f9b993ae82c55a57e09774f80d26e236a0ba4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.
Transparency logSecurity for certmate-cli 0.1.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for certmate_cli-0.1.6.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.