flashbots / flashbots/glycerine
chore: switch to `backon` crate
Open
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Probably not an issue since its quite a simple crate, but for audit consider switching to backon: https://rustsec.org/advisories/RUSTSEC-2025-0012.html
_Originally posted by @ameba23 in https://github.com/flashbots/glycerine/pull/1#discussion_r3541808945_
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is named. Start by locating the current retry dependency and reviewing the linked RustSec advisory and `backon` crate; done means the dependency is switched without breaking the existing project checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100