The repository or configuration that created this release differ from a previous release. View details.
requirements-as-code → rac-core
This package has been renamed.
requirements-as-codeis now published asrac-core.
pip install rac-core
The import package and CLI are unchanged — you still import rac and run rac.
Only the PyPI distribution name changed (see ADR-092).
This release of requirements-as-code is a transitional redirect: it contains
no code of its own and simply depends on rac-core, so existing
pip install requirements-as-code and CI keep working. It will not be updated
further — point new installs at rac-core.
1 maintainer
Metadata
1 maintainer
Release files for requirements-as-code 2026.6.99
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Change of provenance
The repository or configuration that created these release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| requirements_as_code-2026.6.99.tar.gz | 2.1 kB | With provenance | Details for requirements_as_code-2026.6.99.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| requirements_as_code-2026.6.99-py3-none-any.whl | Python 3 | none | any | Details for requirements_as_code-2026.6.99-py3-none-any.whl |
Total release size: 3.7 kB
Release files / requirements_as_code-2026.6.99.tar.gz
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | requirements_as_code-2026.6.99.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e8684f489d1603f66c0168ab0be3b1c86dde85c945934407737106c62b92401
|
|
BLAKE2b-256 checksum How to use checksums |
62f4eb10579386b7f4e21e6473078ed5170498edcd17ad69c73684fcda2016e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 27, 2026.
Transparency logRelease files / requirements_as_code-2026.6.99-py3-none-any.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | requirements_as_code-2026.6.99-py3-none-any.whl |
|---|---|
| Size | 1.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1b57a5bbff9f0f8f34ceb02c4e495d0e153eb281ac29000a40a340b867dd95bd
|
|
BLAKE2b-256 checksum How to use checksums |
40ff4c1345a9a57506391f1d97fe0c221115b9db5675f0ceb04c7ea4d44a79a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 27, 2026.
Transparency logSecurity for requirements-as-code 2026.6.99
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.
Change of provenance
The configuration that created this release differs from a previous release.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Attestation for requirements_as_code-2026.6.99.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 Jun 27, 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.
