0.1.12 (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
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 Instant is 0.1.13.
0.1.12 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
0.1.12 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.1.9 (older version)
From google/supply-chain copy of chromium. Audited without comment by Android 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 impliescrypto-safe, but does not require expert review in order to audit for.- 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 Instant is 0.1.13.
0.1.11 (older version) Thoroughness: Low Understanding: Medium
by leo60228 on 2021-09-28
just refactoring
0.1.2 (older version) Thoroughness: Medium Understanding: High
by MaulingMonkey on 2019-10-13
std::time::Instant alternative that doesn't panic on wasm targets.
Pros:
- Doesn't panic!
- Just std::time::Instant on native, no performance hit or anything
Cons:
- Just std::time::Instant on native, easy to accidentally use new std APIs unavailable on wasm
- f64 repr for Instant makes me nervous
- Unusual license choice for rust projects
- Could use more test coverage
| File | Rating | Notes |
|---|---|---|
| .circleci/config.yml | +1 | |
| src/lib.rs | +1 | |
| src/native.rs | +1 | I would've preferred a wrap Instant for ensuring compat, but sure. |
| src/wasm.rs | 0 | f64 repr might accumulate poorly |
| tests/wasm.rs | 0 | test_instant_now could spuriously fail if elapsed() == 0, would like to see more test coverage |
| .cargo_vcs_info.json | +1 | |
| .cargo-ok | +1 | |
| .gitignore | +1 | Overkill |
| AUTHORS | +1 | |
| Cargo.lock | 0 | Pointless, shouldn't be part of the package |
| Cargo.toml | +1 | BSD-3-Clause |
| Cargo.toml.orig | +1 | BSD-3-Clause |
| LICENSE | +1 | BSD-3-Clause? |
| README.md | +1 |
| Other | Rating | Notes |
|---|---|---|
| unsafe | +1 | None |
| fs | +1 | None |
| io | +1 | None |
| docs | 0 | Mostly unnecessary |
| tests | 0 | Could use more |
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 instant. Alternatively, you can download the tarball of instant v0.1.13 or view the source online.
Packaged for Debian (stable). Changelog: