OmniRegress
The fast, modern Python & Rust library for all your regression adventures.
OmniRegress: A comprehensive Python & Rust library for all types of regression analysis.
🚀 Update: 4.0.0 Release!
✨ Brand New:
- 🦀 Ridge Regression (L2) — Rust implementation with L2 regularization to reduce overfitting and handle multicollinearity
- 🦀 Lasso Regression (L1) — Rust implementation with L1 regularization for automatic feature selection and sparse solutions
🔵 Basic Regression Models
- [✅] Linear Regression — Fast, pure Rust core. (Usage 🚀)
- [✅] Polynomial Regression — Nonlinear fits, Rust-powered. (Usage 🚀)
- [✅] Logistic Regression — Native Rust, robust binary classification. (Usage 🚀)
- [✅] Ridge Regression (L2) — 🛡️ Regularization to prevent overfitting.(Usage 🚀)
- [✅] Lasso Regression (L1) — ✂️ Feature selection with L1 penalty.(Usage 🚀)
- [🚧] Elastic Net — 🧬 Hybrid L1 + L2 regularization.
🟢 Specialized Regression
- Poisson Regression — 📈 For count data (e.g., website visits).
- Cox Regression — ⏳ Survival/time-to-event analysis.
- Quantile Regression — 🎯 Predicts specific percentiles (e.g., median).
- Bayesian Regression — 🎲 Incorporates prior distributions.
🟠 Nonlinear & ML-Based
- Support Vector Regression (SVR) — 🌀 Kernel magic for complex patterns.
- Decision Tree Regression — 🌳 Hierarchical, rule-based splits.
- Random Forest Regression — 🌲🌲 Ensemble of decision trees.
- Neural Network Regression — 🧠 Deep learning for high-dimensional data.
🟣 Other Advanced Types
- Gaussian Process Regression — 🔮 Probabilistic nonlinear modeling.
- Negative Binomial Regression — 🧮 Overdispersed count data.
- Multinomial Logistic Regression — 🏷️ Multi-class classification.
🧪 Testing
See the test suite: OmniRegress_test
Metadata
Release files for omniregress 4.1.1
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 | Actions Reset |
|---|---|---|---|---|
| omniregress-4.1.1-cp313-cp313-macosx_11_0_arm64.whl | CPython 3.13 | CPython 3.13 | macOS 11.0+ ARM64 | Details for omniregress-4.1.1-cp313-cp313-macosx_11_0_arm64.whl |
| omniregress-4.1.1-cp312-cp312-manylinux_2_34_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.34+ x86-64 | Details for omniregress-4.1.1-cp312-cp312-manylinux_2_34_x86_64.whl |
| omniregress-4.1.1-cp39-cp39-win_amd64.whl | CPython 3.9 | CPython 3.9 | Windows x86-64 | Details for omniregress-4.1.1-cp39-cp39-win_amd64.whl |
Total release size: 744.5 kB
Release files / omniregress-4.1.1-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | omniregress-4.1.1-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 266.0 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1c2011f962bb0608ddd139d7a908d1afa37858ae41a7a6c008211a2d3c1c789c
|
|
BLAKE2b-256 checksum How to use checksums |
6a6f1e9d757c756a53957d1bce7430f57f8ad865ab5295f5b14a130e81e53237
|
| 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 Oct 18, 2025.
Transparency logRelease files / omniregress-4.1.1-cp312-cp312-manylinux_2_34_x86_64.whl
| Download URL | omniregress-4.1.1-cp312-cp312-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 310.8 kB |
| Tags | CPython 3.12 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
7001c41799bb68a6212bf14d2f34aa0db45107ea7913b08b341d1927af2b10de
|
|
BLAKE2b-256 checksum How to use checksums |
a42756b1511f4da66a4e9fb0ac6d84bb2037d2edd3b0bf2a9d5b94af14c388a8
|
| 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 Oct 18, 2025.
Transparency logRelease files / omniregress-4.1.1-cp39-cp39-win_amd64.whl
| Download URL | omniregress-4.1.1-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 167.7 kB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
ec876f9725948ad76e42d6848ed4c8265a1db7055c21800d2ded98b814262044
|
|
BLAKE2b-256 checksum How to use checksums |
7cde4fc017b0a565cc4b8e2d00b2d860424dec49a59b5130874ecbd14f1c343e
|
| 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 Oct 18, 2025.
Transparency logSecurity for omniregress 4.1.1
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 3 files in this release have been uploaded with provenance metadata.
Attestation for omniregress-4.1.1-cp313-cp313-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 Oct 18, 2025.
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.