celine-regorus
Python wheels for regorus built and published by the CELINE project.
This repository is not the upstream source code of regorus. It is an automated packaging repository whose only responsibility is to:
- track upstream releases of
microsoft/regorus - build Python wheels
- publish them to PyPI under the name
celine-regorus
Usage example
See official documentation for usage
from regorus import Engine
engine = Engine()
engine.add_policy_from_file("./policy.rego")
engine.set_input({ hello: "world" })
# Evaluate rule
result = engine.eval_rule("my_rule")
print(result)
Scope and guarantees
- Supported platforms
- Linux x86_64 ✅
- Not supported (by design)
- macOS ❌
- Windows ❌
- Other architectures ❌
If you need additional platforms, please open a PR.
Metadata
Release files for celine-regorus 0.9.1.post20260219101125
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| celine_regorus-0.9.1.post20260219101125-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details |
| celine_regorus-0.9.1.post20260219101125-cp310-abi3-macosx_10_12_x86_64.whl | CPython 3.10 | abi3 | macOS 10.12+ x86-64 | Details |
Total release size: 6.5 MB
Release files / celine_regorus-0.9.1.post20260219101125-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | celine_regorus-0.9.1.post20260219101125-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.2 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9f79df6349f480c8caff1268eb5d7ba07321d9add33f8ad87e7807e50dc26352
|
|
BLAKE2b-256 checksum How to use checksums |
1b2df26c19af27c46362e65f4c5c2cfa9b3c020533a96d7bbd01e154b9183054
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.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.
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 Feb 19, 2026.
Transparency logRelease files / celine_regorus-0.9.1.post20260219101125-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | celine_regorus-0.9.1.post20260219101125-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 3.4 MB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
b378c1960a800f9273948bde733327390a5f85030d2d6d2b6e253535690583c2
|
|
BLAKE2b-256 checksum How to use checksums |
e29e3b0a5cb757104bffc9a974c241f2ef739a05932641eef04cd79f5386f543
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.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.
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 Feb 19, 2026.
Transparency logSecurity for celine-regorus 0.9.1.post20260219101125
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 celine_regorus-0.9.1.post20260219101125-cp310-abi3-macosx_11_0_arm64.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 Feb 19, 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.
