rustsec/advisory-db
1
0
Fork 0
mirror of https://github.com/rustsec/advisory-db.git synced 2026-07-16 00:12:29 -04:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix malicious spelling in contributing guide (#2909)

Browse Source 
Signed-off-by: Yoshiki <yosinn1@gmail.com>
This commit is contained in:
yosinn1-blip
2026-05-24 07:31:49 +09:00
committed by GitHub
parent 130152155e
commit 831c50f4a4
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
CONTRIBUTING.md
View File

@@ -7,7 +7,7 @@ To add an advisory to the RustSec database, open a [Pull Request] against
1. Report the vulnerability upstream according to their security policy. RustSec
maintainers do not have expertise in every crate's internals and so a crate
maintainer can much more efficiently respond. Suspected malicous crates
maintainer can much more efficiently respond. Suspected malicious crates
should instead be [reported to crates.io](https://crates.io/policies/security).
2. Wait for the maintainers to confirm the vulnerability exists.
3. Engage in coordinated disclosure (as applicable) so the vulnerability isn't revealed