rust-cv-convert
Library Listed Dormant
Type conversions among famous Rust computer vision libraries
- Downloads
- 298
- Dependents
- 1
- Stars
- 56
- Forks
- 28
- Contributors
- 5
- Commits
- 191
- Latest release
- 0.26.0 ·
About
cv-convert: Convert computer vision data types in Rust
Type conversions among famous Rust computer vision libraries. It supports the following crates:
Usage
No crates are enabled by default. You must specify which computer vision libraries you want to use as features when adding cv-convert to your project.
[dependencies.cv-convert]
version = 'x.y.z' # Please look up the recent version on crates.io
default-features = false
features = [
'image',
'opencv',
'tch',
'nalgebra',
'ndarray',
'imageproc',
]
The basic features (image, opencv, etc.) enable support for the compatible version ranges of each dependency.
The minimum supported rustc is 1.51. You may use older versions of
the crate (>=0.6) in order to use rustc versions that do not support
const-generics.
Available Features
Core library features
image- Enable image crate support (latest version)imageproc- Enable imageproc crate support (latest version)nalgebra- Enable nalgebra crate support (latest version)ndarray- Enable ndarray crate support (latest version)opencv- Enable opencv crate support (latest version)tch- Enable tch crate support (latest version)
Read the full README
Supported version ranges
image- Supports version >=0.24imageproc- Supports version >=0.22nalgebra- Supports versions >=0.26, <0.33ndarray- Supports version >=0.13opencv- Supports versions >=0.63, <0.89tch- Supports version >=0.13
Example Usage
The crate provides ToCv, TryToCv, AsRefCv, TryAsRefCv traits, which are similar to standard library's Into and TryInto.
use cv_convert::{ToCv, TryToCv};
use nalgebra as na;
use opencv as cv;
// ToCv - infallible conversion
let cv_point = cv::core::Point2d::new(1.0, 3.0);
let na_point: na::Point2<f64> = cv_point.to_cv();
// ToCv - the other direction
let na_point = na::Point2::<f64>::new(1.0, 3.0);
let cv_point: cv::core::Point2d = na_point.to_cv();
// TryToCv - fallible conversion
let na_mat = na::DMatrix::from_vec(2, 3, vec![1.0, 2.0, 3.0, 4.0, 5.0, 6.0]);
let cv_mat = na_mat.try_to_cv()?;
// TryToCv - the other direction
let cv_mat = cv::core::Mat::from_slice_2d(&[&[1.0, 2.0, 3.0], &[4.0, 5.0, 6.0]])?;
let na_mat: na::DMatrix<f64> = cv_mat.try_to_cv()?;
Contribute to this Project
Add support for new dependency versions
Dependencies are now specified using range-based version requirements in cv-convert/Cargo.toml.
To support new versions of a dependency, simply update the version range in the [dependencies] section.
For example, to add support for nalgebra 0.33, update the nalgebra dependency:
[dependencies]
nalgebra = { version = ">=0.26, <0.34", optional = true }
This approach automatically supports all compatible versions within the specified range without needing to generate code for each individual version.
Add a new type conversion
To add a new type conversion, take image::DynamicImage and
opencv::Mat for example. Proceed to cv-convert/src and implement
the code in with_opencv_image.rs because it is a conversion among
opencv and image crates.
Choose ToCv or TryToCv trait and add the trait implementation
on image::DynamicImage and opencv::Mat types. The choice of
ToCv or TryToCv depends on whether the conversion is fallible
or not.
impl ToCv<opencv::Mat> for image::DynamicImage { /* omit */ }
impl ToCv<image::DynamicImage> for opencv::Mat { /* omit */ }
// or
impl TryToCv<opencv::Mat> for image::DynamicImage {
type Error = SomeError;
fn try_to_cv(&self) -> Result<opencv::Mat, Self::Error> { /* omit */ }
}
impl TryToCv<image::DynamicImage> for opencv::Mat {
type Error = SomeError;
fn try_to_cv(&self) -> Result<image::DynamicImage, Self::Error> { /* omit */ }
}
#[cfg(test)]
mod tests {
// Write a test
}
License
MIT license. See LICENSE file.
Compatibility
- Runs on
- CUDA
What shows it
- CUDA: cv-convert feature docs-only (dependency tch)
- Native code
- Optional
- Binds native code: torch-sys (feature docs-only)
- Python bindings
- No Python binding crate found
- License
- MIT
Compare with similar projects
Order: strongest tier first, then most downloads, then name, with unmeasured values last. A library counts downloads over 30 days. An app counts binary downloads per release. An app with none counts its crate downloads over 30 days.
| Project | Downloads | Dependents | Stars | Latest release | Runs on (GPU) | Native code | License |
|---|---|---|---|---|---|---|---|
|
Type conversions among famous Rust computer vision libraries |
298 downloads over 30 days | 1 | 56 | 0.26.0 | CUDA | Binds native code: torch-sys (feature docs-only) | MIT |
|
opencv-rust Featured
Rust bindings for OpenCV |
262,425 downloads over 30 days | 96 | 2,500 | 0.101.1 | GPU support unknown | Build uses a native toolchain: cc, pkg-config, vcpkg | MIT |
|
visioncortex Listed
Semantic Computer Vision |
62,153 downloads over 30 days | 16 | 125 | 0.9.3 | GPU support unknown | No native code found | Apache-2.0 OR MIT |
|
kornia-rs Listed
Low-level computer vision library in Rust |
2,294 downloads over 30 days | 6 | 751 | 0.1.5 | CUDA | Binds native code: glib-sys (feature gstreamer), gobject-sys (feature gstreamer), gstreamer-app-sys (feature gstreamer), gstreamer-base-sys (feature gstreamer), gstreamer-sys (feature gstreamer) and 1 more | Apache-2.0 |
|
Batteries-included pure-Rust computer vision crate |
131 downloads over 30 days | 0 | 1,069 | 0.6.0 | GPU support unknown | No native code found | MIT |
|
An open-source computer vision framework to build and deploy applications in minutes Python bindings |
1 downloads over 30 days | 0 | 855 | 1.11.0 | GPU support unknown | Binds native code: gio-sys, glib-sys, gobject-sys, gstreamer-app-sys, gstreamer-base-sys and 5 more | Apache-2.0 |
Why ListedNo archive, New or Featured rule places it, so it is Listed.
What it lacks for Featured
- It has 0 active dependents and 0 new dependents in 365 days. Featured needs 11 active dependents or 9 new dependents in 365 days. The repository route reads 56 stars, 28 forks and 5 contributors. It needs 4,539 stars, 434 forks and 79 contributors together.
- The project is dormant and not finished. Dormancy rule
What else the check found
- The last activity is on 20 May 2025, 538 days ago. That reaches the 365 days the rules expect, so the project is dormant. Dormancy rule
- The oldest outside issue waits 1112 days for a reply, past the limit of 270. No maintainer replied in 365 days. Rot signals rule
Not measured: Latest release fails cargo check.
Exact rules: Listed, Featured library. The check on applied thresholds version 9.
Every rule outcome, as the check records it
expected-interval: version 0.26.0 base 140, raised to the 365-day floor: E = 365 daysdormancy: last activity 2025-05-20, 538 days ago, E = 365: dormantrot: oldest unanswered issue 1112 days (limit 270), no maintainer reply in 365 daysfeatured: not featured: active_users 0 < 11 and new_adopters 0 < 9 and repository route stars 56 (needs 4539), forks 28 (needs 434), contributors 5 (needs 79); dormant and not stablelisted: listed: no archive, new or featured rule applies
Measurements and sources
Each signal row shows the raw value, its source and the fetch date. The Sources list gathers every distinct source on this page. Movement needs more history.
Sources6 sources
- Description: the crates.io description
- crates.io database dump, fetched
- RustSec advisory database, fetched
- GitHub repository, fetched
- crates.io package, fetched
- GitHub contributors, fetched
Adoption0 active dependents, 0 new dependents in 365 days1 not measured
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| Active dependents | 0 | crates.io database dump | Yes | |
| New dependents (365 days) | 0 | crates.io database dump | Yes | |
| Peak active dependents | 1 | crates.io database dump | Yes | |
| Active dependents as a share of the peak | 1 | crates.io database dump | Yes | |
| Binary downloads per release | Not measured | Yes |
MaintenanceLatest human commit: 17 months ago3 not measured
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| Latest human commit | 2025-05-20 | GitHub repository | Yes | |
| Latest release | 2025-05-20 | crates.io database dump | Yes | |
| First release | 2021-01-15 | crates.io database dump | Yes | |
| Latest version | 0.26.0 | crates.io database dump | Yes | |
| Days the oldest outside issue waits for a reply | 1112 | GitHub repository | Yes | |
| Maintainer replies over 365 days | 0 | GitHub repository | Yes | |
| Repository archived | false | GitHub repository | Yes | |
| Repository gone | false | GitHub repository | Yes | |
| Release commit or manifest in the repo | true | crates.io package | Yes | |
| Published docs | true | crates.io database dump | Yes | |
| Latest release fails cargo check | Not measured | Yes | ||
| Build check date | Not measured | Yes | ||
| Build check toolchain | Not measured | Yes |
SecurityUnpatched vulnerabilities: none
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| Unpatched vulnerabilities past the grace window | none | RustSec advisory database | Yes | |
| RustSec unmaintained advisory | none | RustSec advisory database | Yes | |
| Deprecation notice | none | crates.io database dump | Yes | |
| Deprecated requirement | none | crates.io database dump | Yes |
Distribution35 releases, 298 downloads over 30 days5 not measured
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| Releases | 35 | crates.io database dump | Yes | |
| Downloads over 30 days | 298 | crates.io database dump | Yes | |
| Binary downloads over the last 3 releases | Not measured | Yes | ||
| Homebrew installs on request over 365 days | Not measured | Yes | ||
| Repology repository families | Not measured | Yes | ||
| Docker pull growth over 90 days | Not measured | Yes | ||
| Docker pulls at the growth baseline | Not measured | Yes | ||
| Every version a prerelease | false | crates.io database dump | Yes | |
| Every version 0.0.x | false | crates.io database dump | Yes | |
| Every version yanked | false | crates.io database dump | Yes | |
| Crate deleted from crates.io | false | crates.io database dump | Yes |
Repository56 stars, 28 forks, 5 contributors, 191 commits. Stars alone never qualify a project.
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| GitHub stars | 56 | GitHub repository | Yes — one part of the repository route | |
| GitHub forks | 28 | GitHub repository | Yes — one part of the repository route | |
| Contributors with a GitHub account | 5 | GitHub contributors | Yes — one part of the repository route | |
| Commits on the default branch | 191 | GitHub repository | No | |
| Repository's main crate left out of the entry | none | crates.io database dump | Yes |
Facts that never count
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| License | MIT | crates.io database dump | No | |
| Runs on, from listed crates and their direct dependencies | CUDA | crates.io database dump | No | |
| What shows each backend | CUDA: cv-convert feature docs-only (dependency tch) | crates.io database dump | No | |
| Native code, from listed crates and their dependencies | Binds native code: torch-sys (feature docs-only) | crates.io database dump | No | |
| Python bindings, from direct dependencies of listed crates | No Python binding crate found | crates.io database dump | No | |
| Crates that depend on a listed crate directly | 1 | crates.io database dump | No |
Corrections and review history
No correction applies to this entry.
Judgments
A judgment enters only through an approved issue and a merged pull request.
No judgment applies to this entry.