8.3.0 (older version)
From EmbarkStudios/rust-ecosystem. By Embark.
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 jsonwebtoken is 9.3.1.
8.3.0 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
- Team upload.
- Package jsonwebtoken 8.3.0 from crates.io using debcargo 2.7.0
- update to base64 0.22
7.2.0 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-web)
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- 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
This review is from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.
The current version of jsonwebtoken is 9.3.1.
7.1.2 (older version) Thoroughness: Medium Understanding: Medium
by conradgrobler on 2020-07-28
No unsafe code. Passively maintained.
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 jsonwebtoken. Alternatively, you can download the tarball of jsonwebtoken v9.3.1 or view the source online.
No unsafe usage or ambient capabilities