PolicyEngine US
For microsimulation, use policyengine.py. Society-wide microsimulation — population aggregates and distributional or budgetary impacts — is moving to the managed
policyengine.pybundle, which pins certified, calibration-gated datasets. Direct microsimulation viapolicyengine-us(Microsimulation()) is deprecated and being migrated topolicyengine.py. This package remains the home of the US tax-benefit rules and household-level calculations. Microsimulation results are estimates — inspect dataset calibration at https://calibration-diagnostics.vercel.app/populace.
PolicyEngine US is a microsimulation model of the US state and federal tax and benefit system.
PolicyEngine US supports Python 3.11 through 3.14 and requires pandas 3 or
later. To install, run pip install policyengine-us.
This release requires spm-calculator>=1.1.0,<1.2 (the canonical SPM threshold API, covering 2022–2036).
Previously published country versions retain their original dependency metadata;
when reproducing one of those versions, include the compatible calculator
explicitly, for example:
uv pip install "policyengine-us==1.824.7" "spm-calculator==0.3.1"
To install PolicyEngine US as part of a certified PolicyEngine bundle, use the
bundle installer published by policyengine, for example:
uvx --from policyengine policyengine bundle install --country us --venv .venv
Statutes, forms and agency practice
When a statute conflicts with a regulation, form, instructions, manual or
stated agency practice, PolicyEngine US's rule is to follow the statute.
Forms and instructions fill gaps where the statute is silent. Each such
conflict is recorded in the source-conflict register that PolicyEngine shares
with the Axiom Foundation, including any code that does not follow the rule
yet: known-source-conflicts.yaml in
TheAxiomFoundation/rulespec-us.
For each conflict it gives what each source says, a worked example, the
reading this model takes and why, and the code and tests that implement it.
The code marks the deciding line with # Source conflict <jurisdiction>:<id>. See
CONTRIBUTING.md.
1 maintainer
Metadata
1 maintainer
Release files for policyengine-us 2.104.7
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 |
|---|---|---|---|---|
| policyengine_us-2.104.7.tar.gz | 17.2 MB | With provenance | Details for policyengine_us-2.104.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| policyengine_us-2.104.7-py3-none-any.whl | Python 3 | none | any | Details for policyengine_us-2.104.7-py3-none-any.whl |
Total release size: 39.4 MB
Release files / policyengine_us-2.104.7.tar.gz
| Download URL | policyengine_us-2.104.7.tar.gz |
|---|---|
| Size | 17.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c865c9e6c132480b397111a20fe2b2ac1e4fb48328a940ce4e510e80a5a52b92
|
|
BLAKE2b-256 checksum How to use checksums |
d4f9c94ecfbd769a382fd5231e941cca0d3dc1e4338e2ba9fece3d66da66c4da
|
| 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 7, 2026.
Transparency logRelease files / policyengine_us-2.104.7-py3-none-any.whl
| Download URL | policyengine_us-2.104.7-py3-none-any.whl |
|---|---|
| Size | 22.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ac89190f41f4f36b755ece001a72f11d05370d64cc31557d9b3ef16efe2b5727
|
|
BLAKE2b-256 checksum How to use checksums |
227861bd4337e78080ee61232ab40561ed166acecf54c173457f38fa58e1a52b
|
| 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 7, 2026.
Transparency logSecurity for policyengine-us 2.104.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
Both files in this release have been uploaded with provenance metadata.
Attestation for policyengine_us-2.104.7.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 Nov 7, 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.
