losfair / losfair/sqlite-cache

Cut a new release to allow downstream users to be safe from RUSTSEC-2022-0090

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
25
Forks
2
PR merge metrics
No merged PRs in 30d

Description

The recent dependency bump on rusqlite means this crate's main development branch is no longer vulnerable to [RUSTSEC-2022-0090](https://rustsec.org/advisories/RUSTSEC-2022-0090) via older versions of rusqlite's dependency on a vulnerable version of libsqlite3-sys.

So if a new release could be uploaded to crates.io, downstream users of sqlite-cache can also benefit.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the recent rusqlite dependency bump and the project's release procedure first. The task is done when a new sqlite-cache version is uploaded to crates.io so downstream users receive the dependency update that avoids RUSTSEC-2022-0090.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
release, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.