These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

The current version of libsqlite3-sys is 0.30.1.

0.26.0 (older version) unknown

From kornelski/crev-proofs copy of salsa.debian.org.

Only in debcargo (unstable). Changelog:

  • Package libsqlite3-sys 0.26.0 from crates.io using debcargo 2.6.0
  • Relax bindgen dependency to ">= 0.60, < 1.0"

[ Matthias Geiger ]

  • Team upload.
  • Package libsqlite3-sys 0.26.0 from crates.io using debcargo 2.6.0
  • Drop patches, replace them with a single one for the bindgen update

cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.

ub-risk-2 (implies ub-risk-3)

Negligible unsoundness or average soundness.

Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-2

ub-risk-3 (implies ub-risk-4)
Implied by other criteria

Mild unsoundness or suboptimal soundness.

Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-3

ub-risk-4
Implied by other criteria

Extreme unsoundness.

Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-4

safe-to-deploy (implies safe-to-run)

This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…

safe-to-run
Implied by other criteria

This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…

unknown

May have been packaged automatically without a review


Lib.rs has been able to verify that all files in the crate's tarball are in the crate's repository. Please note that this check is still in beta, and absence of this confirmation does not mean that the files don't match.

Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories, so there is a possibility that published crates have a misleading repository URL, or contain different code from the code in the repository.

To review the actual code of the crate, it's best to use cargo crev open libsqlite3-sys. Alternatively, you can download the tarball of libsqlite3-sys v0.30.1 or view the source online.