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

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.9
File Actions
python_dotenvx-3.0.9-cp38-abi3-win_amd64.whl CPython 3.8 abi3 Windows x86-64 Details for python_dotenvx-3.0.9-cp38-abi3-win_amd64.whl
python_dotenvx-3.0.9-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.9-cp38-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
python_dotenvx-3.0.9-cp38-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl CPython 3.8 abi3 Linux glibc 2.17+ ARM64 Details for python_dotenvx-3.0.9-cp38-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
python_dotenvx-3.0.9-cp38-abi3-macosx_11_0_arm64.whl CPython 3.8 abi3 macOS 11.0+ ARM64 Details for python_dotenvx-3.0.9-cp38-abi3-macosx_11_0_arm64.whl
python_dotenvx-3.0.9-cp38-abi3-macosx_10_12_x86_64.whl CPython 3.8 abi3 macOS 10.12+ x86-64 Details for python_dotenvx-3.0.9-cp38-abi3-macosx_10_12_x86_64.whl

Total release size: 7.2 MB

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

Download URL python_dotenvx-3.0.9-cp38-abi3-win_amd64.whl
Size 1.3 MB
Tags CPython 3.8 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
4abc427c0a7e00cb7f1fad84c72d37dcf090ca44004f0aca156c876414fbc148
BLAKE2b-256 checksum
How to use checksums
12a86e2dfd820a27ba13ad0bde903502ccfedb7f91c1552ecdf5c49a2c8b4ebc
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.9-cp38-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL python_dotenvx-3.0.9-cp38-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 1.6 MB
Tags CPython 3.8 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
1e2b7c45cd30bb678fc2f836354c1223de0dae94a000a66efd319c930291a174
BLAKE2b-256 checksum
How to use checksums
53833bccdda51aec83436ebebfd8275e76680b29eaecbe2edc41a5a446272201
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.9-cp38-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl

Download URL python_dotenvx-3.0.9-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
f1ca5638543fd949cc33ba5a182f73073e51eebc3c1ae16bf17bad003ef54cdc
BLAKE2b-256 checksum
How to use checksums
76f3e515a89c706a124bd4aaff28448b66d49c39fbfca3816145bacf37905928
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.9-cp38-abi3-macosx_11_0_arm64.whl

Download URL python_dotenvx-3.0.9-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
c394c3761f31fa9cc1b63ab935d6f04619d468100ad85a9f7e52d8246d9543c9
BLAKE2b-256 checksum
How to use checksums
594ed8b274f72536b2bb2ca53e78970074b1dc213f1d9f67e295f9a3415469d2
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.9-cp38-abi3-macosx_10_12_x86_64.whl

Download URL python_dotenvx-3.0.9-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
f0fffa44564ceb2f6958954a62512dc84d1bd7a4dc22d1d1c071960a36ab4bc1
BLAKE2b-256 checksum
How to use checksums
b2692cb70a1912ff2c2186ac321510796d05a4acd237b32fb36d1522b8933672
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.9

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