Lint your Python architecture.
Import Linter allows you to impose constraints on the imports between your Python modules.
It also provides a browser-based user interface for exploring the architecture of any Python package.
1 maintainer
Metadata
1 maintainer
Release files for import-linter 2.16
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 |
|---|---|---|---|---|
| import_linter-2.16.tar.gz | 1.4 MB | With provenance | Details for import_linter-2.16.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| import_linter-2.16-py3-none-any.whl | Python 3 | none | any | Details for import_linter-2.16-py3-none-any.whl |
Total release size: 2.1 MB
Release files / import_linter-2.16.tar.gz
| Download URL | import_linter-2.16.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c5bd0d38bdef46c7251120266b3bf72662bc8cd989a8fe461499936e12e8c6fa
|
|
BLAKE2b-256 checksum How to use checksums |
f070ac97afe41a04239a60c9d92fbe593294bf6501309d728af4a400e569d786
|
| 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 6, 2026.
Transparency logRelease files / import_linter-2.16-py3-none-any.whl
| Download URL | import_linter-2.16-py3-none-any.whl |
|---|---|
| Size | 644.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e775602e9214ab3933fc7d2162278ea1f11dd9229c914735c1bda43b94619565
|
|
BLAKE2b-256 checksum How to use checksums |
e1f90f8a5a9a95c2b3b7e87e7406a2941a5620aeaacc4207155d5010263dabb6
|
| 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 6, 2026.
Transparency logSecurity for import-linter 2.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for import_linter-2.16.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 6, 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.
