You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[CII Best Practices: Basics](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#upgrade-basics-1)
@@ -42,7 +42,7 @@ Context:
42
42
43
43
> The project MUST have at least two unassociated significant contributors.
-[CII Best Practices: Basics](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#upgrade-basics-1)
@@ -53,12 +53,13 @@ Context:
53
53
54
54
> The project MUST include a copyright statement in each source file, identifying the copyright holder (e.g., the [project name] contributors).
55
55
56
-
**Meet**
56
+
**Unmet**
57
57
58
58
Context:
59
59
-[CII Best Practices: Basics](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#upgrade-basics-1)
60
60
-[CII Best Practices: Copyright Per File](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#copyright_per_file)
-[Issue to follow up](https://github.com/nodejs/security-wg/issues/1187)
62
63
63
64
> The 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: SPDX-License-Identifier: [SPDX license expression for project](https://spdx.dev/ids/#how)
64
65
@@ -67,6 +68,7 @@ Context:
67
68
Context:
68
69
-[CII Best Practices: Basics](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#upgrade-basics-1)
-[Issue to follow up](https://github.com/nodejs/security-wg/issues/1187)
70
72
71
73
# Change Control
72
74
@@ -90,7 +92,7 @@ Context:
90
92
91
93
> The 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.
92
94
93
-
**Met**
95
+
**Met. Node.js org has enabled 2FA for all the members, see: https://github.com/openjs-foundation/security-collab-space/issues/94#issuecomment-1874627417**
94
96
95
97
Context:
96
98
-[CII Best Practices: Change Control](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#upgrade-change-control-1)
@@ -119,7 +121,7 @@ Context:
119
121
120
122
> The 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 inclusion
121
123
122
-
**Met. Currently the repo is monitored against the OSSF Scorecard, where this is checked every 2 weeks in the Security Team regular meetings. See: https://github.com/nodejs/security-wg/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/tools/ossf_scorecard/report.md**
124
+
**Met. The process is documented: https://github.com/nodejs/node/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/doc/contributing/pull-requests.md#reviewing-pull-requests and we use additional tools like the OSSF Scorecard to monitor it**
123
125
124
126
Context:
125
127
-[CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#upgrade-quality-1)
@@ -157,21 +159,24 @@ Context:
157
159
158
160
> The project MUST have FLOSS automated test suite(s) that provide at least 90% statement coverage if there is at least one FLOSS tool that can measure this criterion in the selected language.
159
161
160
-
**Met. This is part of the CI Checks in place**
162
+
**Met. Report available in https://app.codecov.io/gh/nodejs/node**
161
163
162
164
Context:
163
165
-[CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#upgrade-quality-1)
164
166
-[CII Best Practices: Test Statement Coverage 90%](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#test_statement_coverage90)
-[Issue to follow up](https://github.com/nodejs/security-wg/issues/1187)
169
+
166
170
167
171
> The project MUST have FLOSS automated test suite(s) that provide at least 80% branch coverage if there is at least one FLOSS tool that can measure this criterion in the selected language.
168
172
169
-
**Met. This is part of the CI Checks in place**
173
+
**Met. Report available in https://app.codecov.io/gh/nodejs/node**
170
174
171
175
Context:
172
176
-[CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#upgrade-quality-1)
173
177
-[CII Best Practices: Test Branch Coverage 80%](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#test_branch_coverage80)
-[Issue to follow up](https://github.com/nodejs/security-wg/issues/1188)
175
180
176
181
177
182
# Security
@@ -188,6 +193,8 @@ Context:
188
193
-[CII Best Practices: Security](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#upgrade-security-1)
-[See related question in Silver Criteria](/tools/ossf_best_practices/silver_criteria.md)
196
+
-[Issue to follow up](https://github.com/nodejs/security-wg/issues/1189)
197
+
191
198
192
199
> The 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).
193
200
@@ -208,6 +215,7 @@ Context:
208
215
Context:
209
216
-[CII Best Practices: Security](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#upgrade-security-1)
0 commit comments