Skip to main content

dotenvx

A secure dotenv–from the creator of dotenv.

  • Encrypt
  • Commit
  • Ship

Install · Quickstart

Quickstart

With uv installed, create a project and add python-dotenvx.

uv init hello-dotenvx
cd hello-dotenvx
uv add python-dotenvx

Create these two files in the project directory.

.env

HELLO=World

index.py

import os
from dotenvx import load_dotenv

load_dotenv()

print(f"Hello {os.environ['HELLO']}")

Run the script from that directory.

uv run index.py

The script prints Hello World.

 

Usage

Install dotenvx.

$ curl -sfS https://dotenvx.sh | sh
◈ installed (2.38.2:/usr/local/bin/dotenvx)

Encrypt your secrets in .env files. The values become ciphertext and only your private key can unlock them.

$ dotenvx encrypt
◈ encrypted .env (039 BCA) via .env.keys ⛉

Commit your encrypted .env files with your code. It's safe. Now you can securely share secrets through git.

$ git add .env
$ git commit -m "encrypt .env"

Ship your code and secrets together. Dotenvx uses your private key to decrypt and inject your secrets just-in-time to your code.

$ python index.py
⟐ injected env (2) from .env (039 BCA) via .env.keys ⛉

 

Design

Three widely used and proven primitives make up Dotenvx's design. Git, .env, and secp256k1.

We chose git because it is the best way to deliver digital goods. It is the container ship of the digital world. All code travels on its ships. Why not secrets? Why invent an inferior secrets delivery mechanism when the world class one is right there at your fingertips.

We chose .env because it is the open standard for loading secrets into code. It represents environment variables, the core primitive that all secrets end up injected into at runtime of code.

Lastly, we needed to choose an encryption algorithm. Encryption of the values inside the .env file would allow us to place those values with code, leveraging git's distribution advantages while still following the twelve-factor config – by separating the decryption key from the code (environment).

It was important that we choose a proven, simple, asymmetric standard with small keys. We chose secp256k1, battle-tested by Bitcoin for more than seventeen years. We made cryptography an opinionated choice so developers wouldn't have to. Encryption just worked.

The result is a system built entirely from primitives, developers already understand, and infrastructure they already use. Secrets can travel with code without becoming part of the code. Git distributes them, .env defines how apps consume them, and secp256k1 keeps their values unreadable. The kicker, all this works by setting a single private key on your infrastructure - no more risky async coordination of secrets, no more centralized downtime risk. Your secrets are always just there with your code, ready to be unlocked at runtime.

Read the whitepaper →

 

Metadata

Release files for python-dotenvx 3.0.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for python-dotenvx 3.0.7
File Actions
python_dotenvx-3.0.7-cp38-abi3-win_amd64.whl CPython 3.8 abi3 Windows x86-64 Details for python_dotenvx-3.0.7-cp38-abi3-win_amd64.whl
python_dotenvx-3.0.7-cp38-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.8 abi3 Linux glibc 2.17+ x86-64 Details for python_dotenvx-3.0.7-cp38-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
python_dotenvx-3.0.7-cp38-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl CPython 3.8 abi3 Linux glibc 2.17+ ARM64 Details for python_dotenvx-3.0.7-cp38-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
python_dotenvx-3.0.7-cp38-abi3-macosx_11_0_arm64.whl CPython 3.8 abi3 macOS 11.0+ ARM64 Details for python_dotenvx-3.0.7-cp38-abi3-macosx_11_0_arm64.whl
python_dotenvx-3.0.7-cp38-abi3-macosx_10_12_x86_64.whl CPython 3.8 abi3 macOS 10.12+ x86-64 Details for python_dotenvx-3.0.7-cp38-abi3-macosx_10_12_x86_64.whl

Total release size: 7.1 MB

Release files / python_dotenvx-3.0.7-cp38-abi3-win_amd64.whl

Download URL python_dotenvx-3.0.7-cp38-abi3-win_amd64.whl
Size 1.3 MB
Tags CPython 3.8 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
2b748b1609c91af3e366e7cd3b79b28620f201773f473bf63823c9d1fead7918
BLAKE2b-256 checksum
How to use checksums
55dae03aed5778d45ac6d16366836fe972c166510573a9c5822e7afb364e535a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 14, 2026.

Transparency log

Release files / python_dotenvx-3.0.7-cp38-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL python_dotenvx-3.0.7-cp38-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 1.5 MB
Tags CPython 3.8 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
377c17c9d62c0a88967b75779f8690ddc22d1559f389ebc669f483cd9131cb26
BLAKE2b-256 checksum
How to use checksums
5db1c54f1f794e448f6003d6d693d61d01ed0935f840b44e06157c5c8d5a8cb1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 14, 2026.

Transparency log

Release files / python_dotenvx-3.0.7-cp38-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl

Download URL python_dotenvx-3.0.7-cp38-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
Size 1.5 MB
Tags CPython 3.8 Linux glibc 2.17+ ARM64 abi3
SHA-256 checksum
How to use checksums
225e0b2c32e032b6fea5312a45ef5d81ef9b1a1c28945e23c298c9d1c1dccd1a
BLAKE2b-256 checksum
How to use checksums
bf6aa858ac8a575bf117b73adc1c55e5f46766803ac4993f688c424f17cbe069
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 14, 2026.

Transparency log

Release files / python_dotenvx-3.0.7-cp38-abi3-macosx_11_0_arm64.whl

Download URL python_dotenvx-3.0.7-cp38-abi3-macosx_11_0_arm64.whl
Size 1.4 MB
Tags CPython 3.8 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
378463791e5c5bcdc283d9bf7f0e209cbc4a44fb85f58eb108dee122fc0eef88
BLAKE2b-256 checksum
How to use checksums
f549e45e28dda4a57b522586c13ef6970630824cb1038529e81323be6efd0197
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 14, 2026.

Transparency log

Release files / python_dotenvx-3.0.7-cp38-abi3-macosx_10_12_x86_64.whl

Download URL python_dotenvx-3.0.7-cp38-abi3-macosx_10_12_x86_64.whl
Size 1.4 MB
Tags CPython 3.8 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
c6e5db0c4d95d2475e1e42db05da5ea39d1c543ea1319754c3e0c1fc81272577
BLAKE2b-256 checksum
How to use checksums
79f35c72aaa66899ba5d68b9f173611e125e89fc6abb10a3966252adeb9c1fab
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 14, 2026.

Transparency log

Security for python-dotenvx 3.0.7

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

All 5 files in this release have been uploaded with provenance metadata.

Select from 5 files

Attestation for python_dotenvx-3.0.7-cp38-abi3-win_amd64.whl

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 Nov 14, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page