Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecated/unmaintained dependencies and other issues #110

Closed
DuckDuckWhale opened this issue Sep 17, 2023 · 2 comments · Fixed by #119
Closed

Deprecated/unmaintained dependencies and other issues #110

DuckDuckWhale opened this issue Sep 17, 2023 · 2 comments · Fixed by #119
Milestone

Comments

@DuckDuckWhale
Copy link

failure is deprecated and unmaintained: rust-lang-deprecated/failure#347

Other issues found via cargo-audit seems to be solved on the newest commit, however there isn't a new crates.io release. There's still one issue left though:

    Fetching advisory database from `https://github.com/RustSec/advisory-db.git`
      Loaded 570 security advisories (from /home/jason/.cargo/advisory-db)
    Updating crates.io index
    Scanning Cargo.lock for vulnerabilities (145 crate dependencies)
Crate:     time
Version:   0.1.45
Title:     Potential segfault in the time crate
Date:      2020-11-18
ID:        RUSTSEC-2020-0071
URL:       https://rustsec.org/advisories/RUSTSEC-2020-0071
Severity:  6.2 (medium)
Solution:  Upgrade to >=0.2.23
Dependency tree:
time 0.1.45
└── chrono 0.4.29
    └── fern 0.5.9
        └── cargo-sweep 0.6.2

error: 1 vulnerability found!

This remaining one can be resolved by updating to the newest fern version.

@marcospb19
Copy link
Collaborator

Thanks, I'll postpone 0.7.0 until I take a better look at this.

@marcospb19 marcospb19 added this to the 0.7.0 milestone Sep 18, 2023
@marcospb19
Copy link
Collaborator

Hey, we're not using failure, right? So it's just the fern problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants