Secure development knowledge
Unknown required information, not enough for a badge.
Met
Unmet
?
The project MUST have at least one primary developer who knows how to design secure software. (See ‘details’ for the exact requirements.) [know_secure_design]
Unknown required information, not enough for a badge.
Met
Unmet
?
At least one of the project's primary developers MUST know of common kinds of errors that lead to vulnerabilities in this kind of software, as well as at least one method to counter or mitigate each of them. [know_common_errors]
Use basic good cryptographic practices
Note that some software does not need to use cryptographic mechanisms. If your project produces software that (1) includes, activates, or enables encryption functionality, and (2) might be released from the United States (US) to outside the US or to a non-US-citizen, you may be legally required to take a few extra steps. Typically this just involves sending an email. For more information, see the encryption section of Understanding Open Source Technology & US Export Controls.
Unknown required information, not enough for a badge.
Met
Unmet
N/A
?
The software produced by the project MUST use, by default, only cryptographic protocols and algorithms that are publicly published and reviewed by experts (if cryptographic protocols and algorithms are used). [crypto_published]
Unknown required information, not enough for a badge.
Met
Unmet
N/A
?
If the software produced by the project is an application or library, and its primary purpose is not to implement cryptography, then it SHOULD only call on software specifically designed to implement cryptographic functions; it SHOULD NOT re-implement its own. [crypto_call]
Unknown required information, not enough for a badge.
Met
Unmet
N/A
?
All functionality in the software produced by the project that depends on cryptography MUST be implementable using FLOSS. [crypto_floss]
Unknown required information, not enough for a badge.
Met
Unmet
N/A
?
The security mechanisms within the software produced by the project MUST use default keylengths that at least meet the NIST minimum requirements through the year 2030 (as stated in 2012). It MUST be possible to configure the software so that smaller keylengths are completely disabled. [crypto_keylength]
Unknown required information, not enough for a badge.
Met
Unmet
N/A
?
The default security mechanisms within the software produced by the project MUST NOT depend on broken cryptographic algorithms (e.g., MD4, MD5, single DES, RC4, Dual_EC_DRBG), or use cipher modes that are inappropriate to the context, unless they are necessary to implement an interoperable protocol (where the protocol implemented is the most recent version of that standard broadly supported by the network ecosystem, that ecosystem requires the use of such an algorithm or mode, and that ecosystem does not offer any more secure alternative). The documentation MUST describe any relevant security risks and any known mitigations if these broken algorithms or modes are necessary for an interoperable protocol. [crypto_working]
Unknown required information, not enough for a badge.
Met
Unmet
N/A
?
The default security mechanisms within the software produced by the project SHOULD NOT depend on cryptographic algorithms or modes with known serious weaknesses (e.g., the SHA-1 cryptographic hash algorithm or the CBC mode in SSH). [crypto_weaknesses]
Unknown required information, not enough for a badge.
Met
Unmet
N/A
?
The security mechanisms within the software produced by the project SHOULD implement perfect forward secrecy for key agreement protocols so a session key derived from a set of long-term keys cannot be compromised if one of the long-term keys is compromised in the future. [crypto_pfs]
Unknown required information, not enough for a badge.
Met
Unmet
N/A
?
If the software produced by the project causes the storing of passwords for authentication of external users, the passwords MUST be stored as iterated hashes with a per-user salt by using a key stretching (iterated) algorithm (e.g., Argon2id, Bcrypt, Scrypt, or PBKDF2). See also OWASP Password Storage Cheat Sheet. [crypto_password_storage]
Unknown required information, not enough for a badge.
Met
Unmet
N/A
?
The security mechanisms within the software produced by the project MUST generate all cryptographic keys and nonces using a cryptographically secure random number generator, and MUST NOT do so using generators that are cryptographically insecure. [crypto_random]
Secured delivery against man-in-the-middle (MITM) attacks
Enough for a badge!
Met
Unmet
?
The project MUST use a delivery mechanism that counters MITM attacks. Using https or ssh+scp is acceptable. [delivery_mitm]
Distribution channels use HTTPS exclusively. [osps_br_03_02]
Unknown required information, not enough for a badge.
Met
Unmet
?
A cryptographic hash (e.g., a sha1sum) MUST NOT be retrieved over http and used without checking for a cryptographic signature. [delivery_unsigned]
Publicly known vulnerabilities fixed
Unknown required information, not enough for a badge.
Met
Unmet
?
There MUST be no unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days. [vulnerabilities_fixed_60_days]
Unknown required information, not enough for a badge.
Met
Unmet
?
Projects SHOULD fix all critical vulnerabilities rapidly after they are reported. [vulnerabilities_critical_fixed]
Other security issues
Unknown required information, not enough for a badge.
Met
Unmet
?
The public repositories MUST NOT leak a valid private credential (e.g., a working password or private key) that is intended to limit public access. [no_leaked_credentials]
Предупреждение: требуется URL, но URL не найден.
. Вы также можете просмотреть критерии уровня 
или 
.