Code reviews of the libdbus-sys crate // Lib.rs

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

0.2.5 (current) safe-to-run, does-not-implement-crypto

From google/supply-chain copy of chromium. By George Burgess IV.

This audit does not include an audit of the vendor/ directory, which contains a full copy of dbus, but is only built when the vendored feature is enabled.

0.2.5 (current) unknown

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

Only in debcargo (unstable). Changelog:

Team upload.
Package libdbus-sys 0.2.5 from crates.io using debcargo 2.7.0
Exclude vendored dbus from source tarball
Collapsed features in debcargo.toml
Add patch to strip vendored feature
Mark standalone feature as flaky

0.2.5 (current) unknown

From kornelski/crev-proofs copy of git.savannah.gnu.org.

Packaged for Guix (crates-io)

The current version of libdbus-sys is 0.2.5.

0.2.2 (older version) safe-to-run

From google/supply-chain copy of chromium. Audited without comment by ChromeOS Legacy.

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

safe-to-run

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

does-not-implement-crypto (implies crypto-safe)

Inspection reveals that the crate in question does not attempt to implement any cryptographic algorithms on its own.

Note that certification of this does not require an expert on all forms of cryptography: it's expected for crates we import to be "good enough" citizens, so they'll at least be forthcoming if they try to implement something cryptographic. When in doubt, please ask an expert.

crypto-safe

Implied by other criteria

All crypto algorithms in this crate have been reviewed by a relevant expert.

Note: If a crate does not implement crypto, use does-not-implement-crypto, which implies crypto-safe, but does not require expert review in order to audit for.

unknown

May have been packaged automatically without a review

Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories. There is absolutely no guarantee that the repository URL declared by the crate belongs to the crate, or that the code in the repository is the code inside the published tarball.

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

The crate tarball contains, among others, this file:

obscure autoconf code, 64KB: vendor/dbus/configure.ac