Skip to main content

PolicyEngine US

codecov PyPI version Code style: ruff

For microsimulation, use policyengine.py. Society-wide microsimulation — population aggregates and distributional or budgetary impacts — is moving to the managed policyengine.py bundle, which pins certified, calibration-gated datasets. Direct microsimulation via policyengine-us (Microsimulation()) is deprecated and being migrated to policyengine.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.

Metadata

Release files for policyengine-us 2.135.3

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

Source distribution (sdist)

Source distribution for policyengine-us 2.135.3
File Size Uploaded Provenance Actions
policyengine_us-2.135.3.tar.gz 19.4 MB With provenance Details for policyengine_us-2.135.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for policyengine-us 2.135.3
File Interpreter ABI Platform Actions
policyengine_us-2.135.3-py3-none-any.whl Python 3 none any Details for policyengine_us-2.135.3-py3-none-any.whl

Total release size: 44.4 MB

Release files / policyengine_us-2.135.3.tar.gz

Download URL policyengine_us-2.135.3.tar.gz
Size 19.4 MB
Tags Source
SHA-256 checksum
How to use checksums
14049b960f226165984976944bd27798c1187dfd33791b81d20204fc83d3ac61
BLAKE2b-256 checksum
How to use checksums
635b37fe3c9d41446edf2393561e30d0654fe048589e191bcf93005a0f4c25db
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 15, 2026.

Transparency log

Release files / policyengine_us-2.135.3-py3-none-any.whl

Download URL policyengine_us-2.135.3-py3-none-any.whl
Size 25.0 MB
Tags Python 3
SHA-256 checksum
How to use checksums
e77f870115b14b81b84927d08f39df974b09d2f0a89656f8b55c142a0849cc6b
BLAKE2b-256 checksum
How to use checksums
fe0e615e1dcd4dd05b608305e21c36fef44a786ef343f6dc77f4117bd7bba8e7
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 15, 2026.

Transparency log

Security for policyengine-us 2.135.3

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.

Select from 2 files

Attestation for policyengine_us-2.135.3.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 15, 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.

Release history Release notifications | RSS feed

This release

2.135.3 This release

2 release files Full provenance

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