aws-samples / aws-samples/sample-code-for-a-secure-vault-using-aws-nitro-enclaves
RUSTSEC-2022-0077: `claim` is Unmaintained
- Dominant language
- Rust
- Stars
- 9
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
> `claim` is Unmaintained
| Details | |
| ------------------- | ---------------------------------------------- |
| Status | unmaintained |
| Package | `claim` |
| Version | `0.5.0` |
| URL | [https://github.com/svartalf/rust-claim/issues/12](https://github.com/svartalf/rust-claim/issues/12) |
| Date | 2022-12-04 |
The last release was in February 2021, almost two years ago.
The maintainer has been unresponsive regarding this crate for over a year.
A pending issue with `claim`'s dependencies has made the crate [difficult to use](https://github.com/svartalf/rust-claim/issues/9).
## Possible Alternative(s)
The below list has not been vetted in any way and may or may not contain alternatives;
- [`claims`](https://crates.io/crates/claims), a direct fork of the `claim` crate
See [advisory page](https://rustsec.org/advisories/RUSTSEC-2022-0077.html) for additional details.
Contributor guide
Research direction
Start by locating the repository's references to the unmaintained `claim` package and read the linked advisory and possible `claims` alternative. Determine how the dependency is used, then update or replace it so the advisory no longer applies and verify the project still builds and its existing checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100