Lib.rs

› AutoCfg › Reviews

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 AutoCfg is 1.4.0.

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.

ub-risk-0 (implies ub-risk-1)

No unsafe code.

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

ub-risk-1 (implies ub-risk-2)
Implied by other criteria

Excellent 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-1

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

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…

unknown

May have been packaged automatically without a review

These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.

The current version of AutoCfg is 1.4.0.

1.1.0 (older version) Rating: Positive Thoroughness: Medium Understanding: Medium

Approved without comment by johnlepikhin on 2022-11-04

1.0.1 (older version) Rating: Positive Thoroughness: Medium Understanding: Medium

Approved without comment by inflation on 2021-11-08

1.0.1 (older version) Rating: Positive Thoroughness: Low Understanding: Medium

Approved without comment by kornelski on 2021-02-24

1.0.1 (older version) Rating: Positive Thoroughness: Low Understanding: Medium

by Minoru on 2021-02-15

No unsafe code. The rest looks benign: the crate emits little bits of code and runs them through the compiler to detect features. The test suite is minimal but looks complete.

1.0.0 (older version) Rating: Positive Thoroughness: Medium Understanding: High

by niklasf on 2020-01-18

autocfg is a small and simple crate to be used in build scripts.

Code snippets are passed to rustc to detect if the available version supports the desired features and can compile them. For completeness, it should be mentioned that it would be a bad idea to use this with user inputs at runtime. It is hard to do so accidantely.

0.1.7 (older version) Rating: Positive Thoroughness: Medium Understanding: Medium

by MaulingMonkey on 2019-12-22

LGTM, starts using RUSTFLAGS

0.1.6 (older version) Rating: Positive Thoroughness: Medium Understanding: Medium

by MaulingMonkey on 2019-09-03

Show review…

0.1.6: LGTM 0.1.5: No unsafe code, minor safe-looking file I/O

0.1.6 (older version) Rating: Positive Thoroughness: Medium Understanding: Medium

by git.sr.ht/~icefox on 2019-08-30

Reads env vars and executes the program in them, or whatever program happens to be called rustc... but given that this thing's purpose is to probe rustc versions, that's kinda inevitable. Abuseable but certainly not malicious; it's made for build scripts and it's fine for this purpose.

Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock, are in the crate's repository with a git tag matching the version. 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 autocfg. Alternatively, you can download the tarball of autocfg v1.4.0 or view the source online.