pyavd-utils 🦀
⚠️ Danger
This package is an internal dependency designed solely for the use of the pyavd Python library. It exposes low-level functionality and is not intended for direct use by end-users.
Purpose
pyavd-utils provides functionalities in Rust for the Python package, PyAVD.
PyAVD is designed to expose the core logic of the AVD Ansible collection (arista.avd) as a standalone, dependency-lite Python library. This allows developers to utilize AVD's complex data processing capabilities—like input validation, AVD facts generation, and structured configuration generation—within custom Python applications without requiring a full Ansible installation or runtime.
This repository, pyavd-utils, provides functionalities to PyAVD, specifically handling the heavy lifting of data structure validation and manipulation with the speed and safety guarantees of Rust.
Schema compilation and source-code generation are distributed separately as pyavd-utils-gen.
The generation package pins the matching pyavd-utils release and is only needed by AVD's
development and build tooling; pyAVD runtime installations do not need it.
Contribution and Development
We welcome contributions to the pyavd-utils project. As this is a performance-focused component, any contributions should include thorough testing and benchmarking to ensure stability and verify performance improvements.
Please refer to the main AVD GitHub repository for general contribution guidelines.
Merge queue
Once the merge queue is enabled for main, maintainers can enqueue a pull request after its required reviews and checks pass.
The queue runs required-checks and Autofix - run pre-commit on a temporary commit containing the latest main and preceding queued changes.
Successful pull request checks do not replace this validation, and contributors do not need to update their branch just because main advances.
If a pull request leaves the queue because validation fails, inspect the failed run, fix the cause, and enqueue it again after its checks pass. Pre-commit failures block the queue run; autofix commits are only submitted outside merge-group runs. Avoid routinely jumping to the front of the queue, because reordering rebuilds the entries behind it.
License
pyavd-utils is licensed under Apache2. See the LICENSE file for details.
3 maintainers
Metadata
3 maintainers
Release files for pyavd-utils 0.0.14
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
Total release size: 10.3 MB
Release files / pyavd_utils-0.0.14-cp310-abi3-win_amd64.whl
| Download URL | pyavd_utils-0.0.14-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
35cc840f5bb52249b3589d7e6050d97b5bf98d5cedd5a3595f693f5f43176177
|
|
BLAKE2b-256 checksum How to use checksums |
b4d5bf72d0a5b6e5ab338131e50c46f6781a5d54898fc95d83e14f5e466431c9
|
| 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 5, 2026.
Transparency logRelease files / pyavd_utils-0.0.14-cp310-abi3-musllinux_1_2_x86_64.whl
| Download URL | pyavd_utils-0.0.14-cp310-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
22b00c0000db4f06df79a981d55bdbc0795cc88ed959e5aec9a30133c9e4fbf0
|
|
BLAKE2b-256 checksum How to use checksums |
5345b5e5f7cb4d378585428994101a4c9eab4f4e90e6fffb91c4e708a95a6f6c
|
| 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 5, 2026.
Transparency logRelease files / pyavd_utils-0.0.14-cp310-abi3-musllinux_1_2_aarch64.whl
| Download URL | pyavd_utils-0.0.14-cp310-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.10 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
fb036bfb41533367f552598cb2a312d6bb71acffc93c6e4d3297293b3278baf2
|
|
BLAKE2b-256 checksum How to use checksums |
d68ab1baca536ed627a55585d68f4b138fb070e8aac52dee41f19762ec5268a7
|
| 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 5, 2026.
Transparency logRelease files / pyavd_utils-0.0.14-cp310-abi3-manylinux_2_28_x86_64.whl
| Download URL | pyavd_utils-0.0.14-cp310-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
03fd06552b1da73ed03ae16a61f68aa0209e13b1ce3548f44de16a5737aaa293
|
|
BLAKE2b-256 checksum How to use checksums |
9446e389d6c8e317b49f9b45d3c074dbfd3cb71ccc010c6dd9ad5afba8e908df
|
| 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 5, 2026.
Transparency logRelease files / pyavd_utils-0.0.14-cp310-abi3-manylinux_2_28_aarch64.whl
| Download URL | pyavd_utils-0.0.14-cp310-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
81ecf1581b5b95a999146bb12544ffd0fbaa3a95ee560def5a8c67f5a21b719e
|
|
BLAKE2b-256 checksum How to use checksums |
e1288339e207e7892a2845b2e72e30eace81a4a4f03396cfef3688cba262ff1a
|
| 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 5, 2026.
Transparency logRelease files / pyavd_utils-0.0.14-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | pyavd_utils-0.0.14-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
fd1f3cdf18b1b4a0c6ce11be77d0b15ee2b31e617155397d04371856679e963e
|
|
BLAKE2b-256 checksum How to use checksums |
4a3ad520cc0500de271e35ef05bc48264864290d4de047f08d77b040d8c6c0f2
|
| 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 5, 2026.
Transparency logRelease files / pyavd_utils-0.0.14-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | pyavd_utils-0.0.14-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
53f24db3790eb52bffbb588ec5d798a156dfbf538685572393fcf6e8f39061bd
|
|
BLAKE2b-256 checksum How to use checksums |
7b22a99a8d61ba333a08011317ad653d77f80a1e43da8ad8df565bb9d5d3d463
|
| 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 5, 2026.
Transparency logSecurity for pyavd-utils 0.0.14
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 7 files in this release have been uploaded with provenance metadata.
Attestation for pyavd_utils-0.0.14-cp310-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 5, 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.
