RUSTSEC-2023-0089: atomic-polyfill is unmaintained
- Dominant language
- Rust
- Stars
- 56.8k
- Forks
- 2.9k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 5
Description
> atomic-polyfill is unmaintained
| Details | |
| ------------------- | ---------------------------------------------- |
| Status | unmaintained |
| Package | `atomic-polyfill` |
| Version | `1.0.3` |
| URL | [https://github.com/embassy-rs/atomic-polyfill/commit/48e55c166684f37af0b00fbee5a0809b1a2bae8e](https://github.com/embassy-rs/atomic-polyfill/commit/48e55c166684f37af0b00fbee5a0809b1a2bae8e) |
| Date | 2023-07-11 |
The author has archived the GitHub repository and mentions deprecation in
project's
[README](https://github.com/embassy-rs/atomic-polyfill/blob/48e55c166684f37af0b00fbee5a0809b1a2bae8e/README.md).
## Possible alternatives
* [portable-atomic](https://crates.io/crates/portable-atomic)
See [advisory page](https://rustsec.org/advisories/RUSTSEC-2023-0089.html) for additional details.
Contributor guide
Research direction
Start by checking the repository's dependency manifests for atomic-polyfill and identify where the package is used. Read the atomic-polyfill README and the linked RustSec advisory, then evaluate portable-atomic as the stated alternative. Done means the unmaintained dependency is no longer required and the relevant checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100