LukeMathWalker / LukeMathWalker/wiremock-rs
RUSTSEC-2025-0007: *ring* is unmaintained
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 799
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
> *ring* is unmaintained
| Details | |
| ------------------- | ---------------------------------------------- |
| Status | unmaintained |
| Package | `ring` |
| Version | `0.17.10` |
| URL | [https://github.com/briansmith/ring/discussions/2414](https://github.com/briansmith/ring/discussions/2414) |
| Date | 2025-02-20 |
The author has announced an indefinite hiatus in its development, noting that
any reported security vulnerabilities may go unaddressed for prolonged periods
of time.
See [advisory page](https://rustsec.org/advisories/RUSTSEC-2025-0007.html) for additional details.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked RUSTSEC-2025-0007 advisory and the referenced ring discussion. Then inspect the repository's dependency configuration and tests to determine how ring is used; the issue does not define a replacement or other completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100