ABCDEFGIKMOQSUWYAAAC
1
Weights-10.51NOTE: DO NOT UPDATE HERE - Instead update your badge by clicking on the links to the right --->OpenEXROpenColorIOOpenVDBOpenCueMaterialXOpen Shading LanguageOpenImageIOOpenAssetIOOpenTimelineIORezDPEL
2
Totals requirements Unmet and Required/MUSTs07953681319193
3
LevelMet or N/AUnsureNot MetScoreRequired?DescriptionStatusStatusStatusStatusStatusStatusStatusStatusStatusStatusStatus
9
Silver2097YesThe project MUST cryptographically sign releases of the project results intended for widespread use, and there MUST be a documented process explaining to users how they can obtain the public signing keys and verify the signature(s). The private key for these signature(s) MUST NOT be on site(s) used to directly distribute the software to the public. If releases are not intended for widespread use, select not applicable" (N/A)."MetUnmetUnmetUnmetUnmetUnmetUnmetUnmetUnmetUnmetMet
13
Gold3085YesHardening mechanisms MUST be used in the software produced by the project so that software defects are less likely to result in security vulnerabilities.MetUnmetUnmetUnmetMetUnmetUnmetUnmetUnmetUnmetN/A
17
Silver5061YesThe project MUST have FLOSS automated test suite(s) that provide at least 80% statement coverage if there is at least one FLOSS tool that can measure this criterion in the selected language.MetUnmetMetUnmetMetMetUnmetUnmetUnmetUnmetN/A
18
Gold5061YesThe project MUST apply at least one dynamic analysis tool to any proposed major production release of the software produced by the project before its release.MetUnmetUnmetUnmetMetMetMetUnmetUnmetUnmetMet
21
Silver5061YesThe project MUST be able to repeat the process of generating information from source files and get exactly the same bit-for-bit result. If no building occurs (e.g., scripting languages where the source code is used directly instead of being compiled), select not applicable" (N/A)."MetUnmetUnmetN/AMetUnmetMetUnmetUnmetUnmetN/A
24
Silver605-1YesThe project MUST document what the user can and cannot expect in terms of security from the software produced by the project (its security requirements")."MetMetMetUnmetMetMetUnmetUnmetUnmetUnmetN/A
25
Silver704-3YesIf the software produced by the project includes software written using a memory-unsafe language (e.g., C or C++), then at least one dynamic tool (e.g., a fuzzer or web application scanner) MUST be routinely used in combination with a mechanism to detect memory safety problems such as buffer overwrites. If the project does not produce software written in a memory-unsafe language, choose not applicable" (N/A)."MetUnmetUnmetN/AMetMetMetUnmetUnmetN/AN/A
27
Silver704-3YesThe project MUST have a documented process for responding to vulnerability reports.MetMetMetMetMetMetMetUnmetUnmetUnmetUnmet
28
Gold803-5YesThe project MUST document its code review requirements, including how code review is conducted, what must be checked, and what is required to be acceptable.MetMetMetMetUnmetMetUnmetMetMetUnmetN/A
29
Silver902-7YesThe project MUST either: <ol>"
<li> make it easy to identify and update reused externally-maintained components; <strong>or</strong></li>"
<li> use the standard components provided by the system or programming language.</li>"
</ol>"
Then if a vulnerability is found in a reused component it will be"
easy to update that component." 		MetMetMetMetMetMetMetMetUnmetUnmetN/A
30
Silver902-7YesProjects MUST monitor or periodically check their external dependencies (including convenience copies) to detect known vulnerabilities, and fix exploitable vulnerabilities or verify them as unexploitable.MetMetMetMetMetMetMetMetUnmetUnmetN/A
31
Silver902-7YesThe project MUST have a documented roadmap that describes what the project intends to do and not do for at least the next year.MetMetUnmetMetMetUnmetMetMetMetMetMet
33
Silver803-5YesThe project MUST automatically enforce its selected coding style(s) if there is at least one FLOSS tool that can do so in the selected language(s).MetUnmetMetMetMetMetMetMetUnmetUnmetN/A
34
Silver803-5YesThe project MUST use at least one static analysis tool with rules or approaches to look for common vulnerabilities in the analyzed language or environment, if there is at least one FLOSS tool that can implement this criterion in the selected language.MetMetMetMetMetMetMetUnmetUnmetUnmetN/A
35
Silver803-5YesThe project MUST achieve a passing level badge.MetMetMetMetMetMetMetMetUnmetUnmetUnmet
37
Passing812-5.5YesThe project MUST publish the process for reporting vulnerabilities on the project site.MetMetMetMetMetMetMetMet?UnmetUnmet
38
Gold1001-9YesThe project MUST have at least 50% of all proposed modifications reviewed before release by a person other than the author, to determine if it is a worthwhile modification and free of known issues which would argue against its inclusionMetMetMetMetUnmetMetMetMetMetMetMet
40
Silver902-7YesThe project MUST provide a quick start" guide for new users to help them quickly do something with the software."MetMetMetMetMetUnmetUnmetMetMetMetN/A
41
Silver902-7YesThe project MUST add regression tests to an automated test suite for at least 50% of the bugs fixed within the last six months.MetMetUnmetMetMetMetMetMetMetUnmetN/A
42
Passing1001-9YesAll medium and higher severity exploitable vulnerabilities discovered with dynamic code analysis MUST be fixed in a timely way after they are confirmed.MetN/AN/AN/AN/AN/AMetMetUnmetN/AN/A
43
Passing911-7.5YesIf private vulnerability reports are supported, the project MUST include how to send the information in a way that is kept private.MetMetN/AMetMetMetMetN/A?UnmetN/A
44
Passing1001-9YesAll medium and higher severity exploitable vulnerabilities discovered with static code analysis MUST be fixed in a timely way after they are confirmed.MetMetMetMetMetMetMetN/AUnmetMetN/A
46
Passing902-7YesAt least one static code analysis tool (beyond compiler warnings and safe" language modes) MUST be applied to any proposed major production release of the software before its release if there is at least one FLOSS tool that implements this criterion in the selected language."MetMetMetMetMetMetMetMetUnmetUnmetN/A
48
Silver1001-9YesThe project MUST include documentation of the architecture (aka high-level design) of the software produced by the project. If the project does not produce software, select not applicable" (N/A)."MetMetMetMetMetMetUnmetMetMetMetN/A
49
Silver1001-9YesThe project MUST provide a way to easily install and uninstall the software produced by the project using a commonly-used convention.MetMetMetMetMetMetUnmetMetMetMetN/A
50
Silver1001-9YesThe project MUST support storing authentication credentials (such as passwords and dynamic tokens) and private cryptographic keys in files that are separate from other information (such as configuration files, databases, and logs), and permit users to update and replace them without code recompilation. If the project never processes authentication credentials and private cryptographic keys, select not applicable" (N/A)."N/AN/AN/AN/AN/AN/AN/AN/AN/AUnmetN/A
51
Silver1100-11YesThe project MUST provide a way for potential developers to quickly install all the project results and support environment necessary to make changes, including the tests and test environment. This MUST be performed with a commonly-used convention.MetMetMetMetMetMetMetMetMetMetN/A
52
Gold1001-9YesThe project MUST clearly identify small tasks that can be performed by new or casual contributors.MetMetMetMetMetUnmetMetMetMetMetMet
54
Silver1001-9YesThe project MUST have a formal written policy that as major new functionality is added, tests for the new functionality MUST be added to an automated test suite.MetMetUnmetMetMetMetMetMetMetMetN/A
55
Silver1001-9YesThe project repository front page and/or website MUST identify and hyperlink to any achievements, including this best practices badge, within 48 hours of public recognition that the achievement has been attained.MetMetMetMetMetMetMetUnmetMetMetMet
56
Gold1001-9YesThe project MUST have at least two unassociated significant contributors.MetMetMetMetMetMetMetUnmetMetMetMet
57
Silver1001-9YesThe project MUST clearly define and document its project governance model (the way it makes decisions, including key roles).MetMetMetMetMetMetMetUnmetMetMetMet
58
Silver1001-9YesThe project MUST clearly define and publicly document the key roles in the project and their responsibilities, including any tasks those roles must perform. It MUST be clear who has which role(s), though this might not be documented in the same way.MetMetMetMetMetMetMetUnmetMetMetMet
59
Gold1001-9YesA test suite MUST be invocable in a standard way for that language.MetMetUnmetMetMetMetMetMetMetMetMet
60
Silver1001-9YesThe project MUST give credit to the reporter(s) of all vulnerability reports resolved in the last 12 months, except for the reporter(s) who request anonymity. If there have been no vulnerabilities resolved in the last 12 months, select not applicable" (N/A)."MetN/AMetMetN/AN/AMetN/AUnmetN/AN/A
61
Passing1001-9YesThe project's initial response time for any vulnerability report received in the last 6 months MUST be less than or equal to 14 days.MetN/AN/AMetMetN/AMetN/AN/AUnmetN/A
62
Passing1001-9YesThe project MUST have at least one primary developer who knows how to design secure software. (See ‘details’ for the exact requirements.)MetMetMetMetMetMetMetMetUnmetMetMet
64
Silver1001-9YesProjects MUST be maximally strict with warnings in the software produced by the project, where practical.MetMetMetMetMetMetMetMetUnmetMetN/A
65
Passing1010-9.5YesThe project MUST address warnings.MetMetMetMetMetMetMetMet?MetN/A
69
Silver1100-11YesThe project MUST make an effort to keep the documentation consistent with the current version of the project results (including software produced by the project). Any <em>known</em> documentation defects making it inconsistent MUST be fixed. If the documentation is generally current, but erroneously includes some older information that is no longer true, just treat that as a defect, then track and fix as usual.MetMetMetMetMetMetMetMetMetMetN/A
70
Silver1100-11YesThe build system for the software produced by the project MUST NOT recursively build subdirectories if there are cross-dependencies in the subdirectories. If there is no build or installation system (e.g., typical JavaScript libraries), select not applicable" (N/A)."MetMetMetN/AMetMetN/AMetMetN/AN/A
71
Gold1100-11YesThe project MUST include a copyright statement in each source file, identifying the copyright holder (e.g., the [project name] contributors).MetMetMetMetMetMetMetMetMetMetMet
72
Gold1100-11YesThe project MUST include a license statement in each source file. This MAY be done by including the following inside a comment near the beginning of each file: <a href=https://spdx.dev/ids/#how"><tt>SPDX-License-Identifier: [SPDX license expression for project]</tt></a>."MetMetMetMetMetMetMetMetMetMetMet
74
Silver1100-11YesThe project MUST include, in its documented instructions for change proposals, the policy that tests are to be added for major new functionality.MetMetMetMetMetMetMetMetMetMetMet
76
Silver1100-11YesThe software produced by the project MUST, if it supports TLS, perform TLS certificate verification by default when using TLS, including on subresources. If the software does not use TLS, select not applicable" (N/A)."N/AN/AN/AN/AN/AN/AN/AN/AN/AMetN/A
77
Silver1100-11YesThe software produced by the project MUST, if it supports TLS, perform certificate verification before sending HTTP headers with private information (such as secure cookies). If the software does not use TLS, select not applicable" (N/A)."N/AN/AN/AN/AN/AN/AN/AN/AN/AMetN/A
80
Gold1100-11YesThe software produced by the project MUST support secure protocols for all of its network communications, such as SSHv2 or later, TLS1.2 or later (HTTPS), IPsec, SFTP, and SNMPv3. Insecure protocols such as FTP, HTTP, telnet, SSLv3 or earlier, and SSHv1 MUST be disabled by default, and only enabled if the user specifically configures it. If the software produced by the project does not support network communications, select not applicable" (N/A)."N/AN/AN/AN/AN/AN/AN/AN/AN/AMetN/A
81
Gold1100-11YesThe software produced by the project MUST, if it supports or uses TLS, support at least TLS version 1.2. Note that the predecessor of TLS was called SSL. If the software does not use TLS, select not applicable" (N/A)."N/AN/AN/AN/AN/AN/AN/AN/AN/AMetN/A
82
Silver1100-11YesBuild systems for native binaries MUST honor the relevant compiler and linker (environment) variables passed in to them (e.g., CC, CFLAGS, CXX, CXXFLAGS, and LDFLAGS) and pass them to compiler and linker invocations. A build system MAY extend them with additional flags; it MUST NOT simply replace provided values with its own. If no native binaries are being generated, select not applicable" (N/A)."MetMetMetN/AMetMetMetMetN/AN/AN/A
84
Silver1100-11YesThe installation system for end-users MUST honor standard conventions for selecting the location where built artifacts are written to at installation time. For example, if it installs files on a POSIX system it MUST honor the DESTDIR environment variable. If there is no installation system or no standard convention, select not applicable" (N/A)."MetMetMetN/AMetMetMetMetMetMetN/A
85
Silver1100-11YesIf the project sites (website, repository, and download URLs) store 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). If the project sites do not store passwords for this purpose, select not applicable" (N/A)."MetMetMetMetMetMetN/AMetMetMetMet
86
Silver1100-11YesThe project MUST maintain the most often used older versions of the product <em>or</em> provide an upgrade path to newer versions. If the upgrade path is difficult, the project MUST document how to perform the upgrade (e.g., the interfaces that have changed and detailed suggested steps to help upgrade).MetMetMetMetMetMetMetMetMetMetN/A
87
Silver1100-11YesThe project MUST identify the specific coding style guides for the primary languages it uses, and require that contributions generally comply with it.MetMetMetMetMetMetMetMetMetMetN/A
88
Gold1100-11YesThe project MUST require two-factor authentication (2FA) for developers for changing a central repository or accessing sensitive data (such as private vulnerability reports). This 2FA mechanism MAY use mechanisms without cryptographic mechanisms such as SMS, though that is not recommended.MetMetMetMetMetMetMetMetMetMetMet
89
Silver1100-11YesThe project MUST adopt a code of conduct and post it in a standard location.MetMetMetMetMetMetMetMetMetMetMet
90
Silver1100-11YesThe project MUST be able to continue with minimal interruption if any one person dies, is incapacitated, or is otherwise unable or unwilling to continue support of the project. In particular, the project MUST be able to create and close issues, accept proposed changes, and release versions of software, within a week of confirmation of the loss of support from any one individual. This MAY be done by ensuring someone else has any necessary keys, passwords, and legal rights to continue the project. Individuals who run a FLOSS project MAY do this by providing keys in a lockbox and a will providing any needed legal rights (e.g., for DNS names).MetMetMetMetMetMetMetMetMetMetMet
92
Gold1100-11YesThe project MUST have a bus factor" of 2 or more."MetMetMetMetMetMetMetMetMetMetMet
94
Passing1100-11YesIf 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 <a href=https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html">OWASP Password Storage Cheat Sheet</a>)."N/AN/AN/AN/AN/AN/AN/AN/AN/AN/AN/A
95
Passing1100-11YesThe 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.N/AN/AN/AN/AN/AN/AN/AN/AN/AN/AN/A
96
Silver1100-11YesAn automated test suite MUST be applied on each check-in to a shared repository for at least one branch. This test suite MUST produce a report on test success or failure.MetMetMetMetMetMetMetMetMetMetMet
97
Passing1100-11YesThe 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).N/AN/AN/AMetN/AN/AN/AN/AN/AN/AN/A
98
Passing1100-11YesAll functionality in the software produced by the project that depends on cryptography MUST be implementable using FLOSS.N/AN/AN/AMetN/AN/AN/AN/AN/AN/AN/A
99
Passing1100-11YesThe 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.N/AN/AN/AMetN/AN/AN/AN/AN/AN/AN/A
102
Passing1100-11YesThe 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.N/AN/AN/AMetN/AN/AN/AN/AN/AMetN/A
104
Passing1100-11YesThe release notes MUST identify every publicly known run-time vulnerability fixed in this release that already had a CVE assignment or similar when the release was created. This criterion may be marked as not applicable (N/A) if users typically cannot practically update the software themselves (e.g., as is often true for kernel updates). This criterion applies only to the project results, not to its dependencies. If there are no release notes or there have been no publicly known vulnerabilities, choose N/A.MetN/AN/AN/AMetN/AMetN/AN/AMetN/A
105
Passing1100-11YesThe project MUST enable one or more compiler warning flags, a safe" language mode or use a separate "linter" tool to look for code quality errors or common simple mistakes if there is at least one FLOSS tool that can implement this criterion in the selected language."MetMetMetMetMetMetMetMetMetN/AN/A
106
Passing1100-11YesThe project MUST provide, in each release, release notes that are a human-readable summary of major changes in that release to help users determine if they should upgrade and what the upgrade impact will be. The release notes MUST NOT be the raw output of a version control log (e.g., the git log" command results are not release notes). Projects whose results are not intended for reuse in multiple locations (such as the software for a single website or service) AND employ continuous delivery MAY select "N/A"."MetMetMetMetMetMetMetN/AMetMetN/A
107
Silver1100-11YesThe default security mechanisms within the software produced by the project MUST 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).N/AN/AN/AMetN/AN/AN/AN/AN/AN/AN/A
108
Silver1100-11YesThe information on how to contribute MUST include the requirements for acceptable contributions (e.g., a reference to any required coding standard).MetMetMetMetMetMetMetMetMetMetMet
110
Passing1100-11YesAt 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.MetMetMetMetMetMetMetMetMetMetMet
111
Passing1100-11YesThere MUST be no unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days.MetMetMetMetMetMetMetMetMetMetMet
113
Silver1100-11YesThe project MUST use an issue tracker for tracking individual issues.MetMetMetMetMetMetMetMetMetMetMet
114
Passing1100-11YesThe project website MUST succinctly describe what the software does (what problem does it solve?).MetMetMetMetMetMetMetMetMetMetMet
115
Passing1100-11YesThe project website MUST provide information on how to: obtain, provide feedback (as bug reports or enhancements), and contribute to the software.MetMetMetMetMetMetMetMetMetMetMet
116
Passing1100-11YesThe project MUST provide reference documentation that describes the external interface (both input and output) of the software produced by the project.MetMetMetMetMetMetMetMetMetMetN/A
118
Passing1100-11YesTo enable collaborative review, the project's source repository MUST include interim versions for review between releases; it MUST NOT include only final releases.MetMetMetMetMetMetMetMetMetMetMet
119
Passing1100-11YesThe project results MUST have a unique version identifier for each release intended to be used by users.MetMetMetMetMetMetMetMetMetMetMet
121
Passing1100-11YesThe project MUST provide a process for users to submit bug reports (e.g., using an issue tracker or a mailing list).MetMetMetMetMetMetMetMetMetMetMet
123
Passing1100-11YesThe project MUST acknowledge a majority of bug reports submitted in the last 2-12 months (inclusive); the response need not include a fix.MetMetMetMetMetMetMetMetMetMetMet
125
Passing1100-11YesThe project MUST have a publicly available archive for reports and responses for later searching.MetMetMetMetMetMetMetMetMetMetMet
126
Passing1100-11YesIf the software produced by the project requires building for use, the project MUST provide a working build system that can automatically rebuild the software from source code.MetMetMetMetMetMetMetMetMetMetN/A
129
Passing1100-11YesThe project MUST use at least one automated test suite that is publicly released as FLOSS (this test suite may be maintained as a separate FLOSS project). The project MUST clearly show or document how to run the test suite(s) (e.g., via a continuous integration (CI) script or via documentation in files such as BUILD.md, README.md, or CONTRIBUTING.md).MetMetMetMetMetMetMetMetMetMetMet
132
Passing1100-11YesThe project MUST have a general policy (formal or not) that as major new functionality is added to the software produced by the project, tests of that functionality should be added to an automated test suite.MetMetMetMetMetMetMetMetMetMetMet
133
Passing1100-11YesThe project MUST have evidence that the <a href=#test_policy">test_policy</a> for adding tests has been adhered to in the most recent major changes to the software produced by the project."MetMetMetMetMetMetMetMetMetMetMet
134
Passing1100-11YesThe project MUST use a delivery mechanism that counters MITM attacks. Using https or ssh+scp is acceptable.MetMetMetMetMetMetMetMetMetMetMet
135
Passing1100-11YesA cryptographic hash (e.g., a sha1sum) MUST NOT be retrieved over http and used without checking for a cryptographic signature.MetMetMetMetMetMetMetMetMetMetMet
136
Passing1100-11YesThe public repositories MUST NOT leak a valid private credential (e.g., a working password or private key) that is intended to limit public access.MetMetMetMetMetMetMetMetMetMetMet
137
Gold1100-11YesThe project MUST implement continuous integration, where new or changed code is frequently integrated into a central code repository and automated tests are run on the result.MetMetMetMetMetMetMetMetMetMetMet
138
Passing1100-11YesThe information on how to contribute MUST explain the contribution process (e.g., are pull requests used?)MetMetMetMetMetMetMetMetMetMetMet
139
Passing1100-11YesThe software produced by the project MUST be released as FLOSS.MetMetMetMetMetMetMetMetMetMetMet
140
Passing1100-11YesThe project MUST post the license(s) of its results in a standard location in their source repository.MetMetMetMetMetMetMetMetMetMetMet
141
Passing1100-11YesThe project MUST provide basic documentation for the software produced by the project.MetMetMetMetMetMetMetMetMetMetMet
142
Passing1100-11YesThe project sites (website, repository, and download URLs) MUST support HTTPS using TLS.MetMetMetMetMetMetMetMetMetMetMet
143
Passing1100-11YesThe project MUST have one or more mechanisms for discussion (including proposed changes and issues) that are searchable, allow messages and topics to be addressed by URL, enable new people to participate in some of the discussions, and do not require client-side installation of proprietary software.MetMetMetMetMetMetMetMetMetMetMet
144
Passing1100-11YesThe project MUST be maintained.MetMetMetMetMetMetMetMetMetMetMet
145
Passing1100-11YesThe project MUST have a version-controlled source repository that is publicly readable and has a URL.MetMetMetMetMetMetMetMetMetMetMet
146
Passing1100-11YesThe project's source repository MUST track what changes were made, who made the changes, and when the changes were made.MetMetMetMetMetMetMetMetMetMetMet