doc-en VS rustsec

Wait, but for as much as just adding an example, isn't it much simpler? I mean, I can just navigate to https://github.com/php/doc-en/blob/master/reference/intl/messageformatter/format-message.xml, edit the existing example and then create a pull request.

But there is. Even better, there is a git repo. Just recently I saw a bad practice of echoing the error message out unconditionally and proposed a fix.

Pull requests allow people to add changes in a different branch of the code and ask to merge with the master branch. There can be discussion before anything is accepted. If you go back to the php example I linked, there is a small discussion.

The PHP docs are on GitHub: https://github.com/php/doc-en (other languages have their own doc- repos)

Well overhaul documentation is totally possible right now, no need to wait for 8.2. You are welcome to contribute in https://github.com/php/doc-en

It's now all on GitHub (both code and issues), with links at the top of every page (I think those currently still link to bugs.php.net which is actively monitored alongside GitHub issues)

fwiw when you made the comment, it wasn't documented that 8.0.0 removed it on the linked-to-page, thanks for making that obvious, just fixed it, https://github.com/php/doc-en/pull/1149

For reference, should have included the link: https://github.com/php/doc-en

cargo-audit is a simple Cargo tool for detecting vulnerable Rust crates. You can install it with cargo install cargo-audit, use cargo audit and you’re done! Any vulnerable crates will appear below, like so:

Further we use cargo-auditable and cargo-audit as part of both our pipeline and regular scanning of all deployed services. This makes our InfoSec and Legal super happy since it means they can also monitor compliance with licenses and patch/update timings.

Yeah your decade old single header libs get so many audits by comparison.

https://github.com/RustSec/rustsec/tree/main/cargo-audit

https://mozilla.github.io/cargo-vet/

cargo is not npm

PSA: before filing CVEs for other people's projects, file an issue with https://rustsec.org instead

Historically, such serious bugs get communicated broadly and addressed very quickly via security advisory blog posts and on https://rustsec.org.

For known vulnerabilities we have the rustsec vulnerability database. You could have a look over there for inspiration. There's also the related cargo-audit for checking dependencies for known vulnerabilities.

Would be cool if this was also reported to https://rustsec.org/ that way cargo audit could pick up and alert the users about it.

P.S. I also made scanning binaries 5x faster in the latest release of cargo audit.

Thanks to cargo and the community, project maintenance is straightforward in rust. You'll need to install cargo-outdated and cargo-audit:

Use the automated tools to assist you in the maintenance of your projects: rustfmt, clippy, cargo update, cargo outdated and cargo-audit.