-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add unmaintained advisory for safemem #1615
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please can we use formatting / fill the necessary detail accordingly per this example:
https://github.com/rustsec/advisory-db/blob/main/crates/buf_redux/RUSTSEC-2023-0028.md
@dignifiedquire I understand both I wonder if This is because if we would merge this anyone using The crate has had some minimal attention like 2019 with basic miri but it's safety related documentation is kinda thin and it uses panics as it's error handling - not drawing any concrete conclusions either way but anyways worth asking 🤷♀️ |
Probably makes sense to either inline or replace. |
The
|
Thanks for the heads-up! I've changed the advisory to only include very obviously correct and uncontroversial statements. I'm going to go ahead and merge this now that we have a clear signal from the maintainer in the form of an archived repo. |
The safemem crate only has three functions, two of which have standard library alternatives by now and one can be workedaround relatively easily. Would it make sense to include some migration instructions in the form of: Migration
|
Sure 👍, feel free to open a PR. |
- as suggested in <#1615 (comment)>
safemem is crate by @abonander who has archived bunch of his Rust crates in GitHub.
See communication attempts on other crates:
multipart
Status #1438