Skip to content

Commit 8e0ea90

Browse files
UlisesGasconUlisesGascon
committed
docs: remark pending justifications
1 parent 7bd3679 commit 8e0ea90

File tree

1 file changed

+20
-20
lines changed

1 file changed

+20
-20
lines changed

‎tools/ossf_best_practices/silver_criteria.md‎

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -240,23 +240,23 @@ Context:
240240

241241
> Build 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).
242242
243-
**Met**
243+
**Met. Warning: Requires lengthier justification.**
244244

245245
Context:
246246
- [CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#quality)
247247
- [Team discussion](https://github.com/nodejs/security-wg/pull/955#discussion_r1197569031)
248248

249249
> The build and installation system SHOULD preserve debugging information if they are requested in the relevant flags (e.g., "install -s" is not used). If there is no build or installation system (e.g., typical JavaScript libraries), select "not applicable" (N/A).
250250
251-
**Met**
251+
**Met. Warning: Requires lengthier justification.**
252252

253253
Context:
254254
- [CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#quality)
255255
- [Team discussion](https://github.com/nodejs/security-wg/pull/955#discussion_r1197569712)
256256

257257
> The 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).
258258
259-
**Met**
259+
**Met. Warning: Requires lengthier justification.**
260260

261261
Context:
262262
- [CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#quality)
@@ -282,7 +282,7 @@ Context:
282282

283283
> The 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).
284284
285-
**Met**
285+
**Met. Warning: Requires lengthier justification.**
286286

287287
Context:
288288
- [CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#quality)
@@ -309,7 +309,7 @@ Context:
309309

310310
> Projects MUST monitor or periodically check their external dependencies (including convenience copies) to detect known vulnerabilities, and fix exploitable vulnerabilities or verify them as unexploitable.
311311
312-
**Met**
312+
**Met. Warning: Requires lengthier justification.**
313313

314314
Context:
315315
- [CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#quality)
@@ -322,15 +322,15 @@ Context:
322322
>
323323
> Then, if a vulnerability is found in a reused component, it will be easy to update that component.
324324
325-
**Met**
325+
**Met. Warning: Requires lengthier justification.**
326326

327327
Context:
328328
- [CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#quality)
329329
- [Team discussion](https://github.com/nodejs/security-wg/pull/955#discussion_r1197572853)
330330

331331
> The project SHOULD avoid using deprecated or obsolete functions and APIs where FLOSS alternatives are available in the set of technology it uses (its "technology stack") and to a supermajority of the users the project supports (so that users have ready access to the alternative).
332332
333-
**Met**
333+
**Met. Warning: Requires lengthier justification.**
334334

335335
Context:
336336
- [CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#quality)
@@ -340,15 +340,15 @@ Context:
340340

341341
> An 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.
342342
343-
**Met**
343+
**Met. Warning: Requires lengthier justification.**
344344

345345
Context:
346346
- [CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#quality)
347347
- [Team discussion](https://github.com/nodejs/security-wg/pull/955#discussion_r1167973646)
348348

349349
> The project MUST add regression tests to an automated test suite for at least 50% of the bugs fixed within the last six months.
350350
351-
**Met**
351+
**Met. Warning: Requires lengthier justification.**
352352

353353
Context:
354354
- [CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#quality)
@@ -367,15 +367,15 @@ Context:
367367

368368
> The 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.
369369
370-
**Met**
370+
**Met. Warning: Requires lengthier justification.**
371371

372372
Context:
373373
- [CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#quality)
374374
- [Team discussion](https://github.com/nodejs/security-wg/pull/955#discussion_r1167973732)
375375

376376
> The project MUST include, in its documented instructions for change proposals, the policy that tests are to be added for major new functionality.
377377
378-
**Met**
378+
**Met. Warning: Requires lengthier justification.**
379379

380380
Context:
381381
- [CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#quality)
@@ -385,7 +385,7 @@ Context:
385385

386386
> Projects MUST be maximally strict with warnings in the software produced by the project, where practical.
387387
388-
**Met**
388+
**Met. Warning: Requires lengthier justification.**
389389

390390
Context:
391391
- [CII Best Practices: Quality](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#quality)
@@ -397,7 +397,7 @@ Context:
397397

398398
> The project MUST implement secure design principles (from "know_secure_design"), where applicable. If the project is not producing software, select "not applicable" (N/A).
399399
400-
**Met**
400+
**Met. Warning: Requires lengthier justification.**
401401

402402
Context:
403403
- [CII Best Practices: Security](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#security)
@@ -409,15 +409,15 @@ _Note that some software does not need to use cryptographic mechanisms. If your
409409

410410
> The 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).
411411
412-
**Met**
412+
**Met. Warning: Requires lengthier justification.**
413413

414414
Context:
415415
- [CII Best Practices: Security](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#security)
416416
- [Team discussion](https://github.com/nodejs/security-wg/pull/955#discussion_r1239561347)
417417

418418
> The project SHOULD support multiple cryptographic algorithms, so users can quickly switch if one is broken. Common symmetric key algorithms include AES, Twofish, and Serpent. Common cryptographic hash algorithm alternatives include SHA-2 (including SHA-224, SHA-256, SHA-384 AND SHA-512) and SHA-3.
419419
420-
**Met**
420+
**Met. Warning: Requires lengthier justification.**
421421

422422
Context:
423423
- [CII Best Practices: Security](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#security)
@@ -441,23 +441,23 @@ Context:
441441

442442
> The software produced by the project SHOULD, 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).
443443
444-
**Met**
444+
**Met. Warning: Requires lengthier justification.**
445445

446446
Context:
447447
- [CII Best Practices: Security](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#security)
448448
- [Team discussion](https://github.com/nodejs/security-wg/pull/955#discussion_r1196319849)
449449

450450
> The 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).
451451
452-
**Met**
452+
**Met. Warning: Requires lengthier justification.**
453453

454454
Context:
455455
- [CII Best Practices: Security](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#security)
456456
- [Team discussion](https://github.com/nodejs/security-wg/pull/955#discussion_r1239563613)
457457

458458
> The 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).
459459
460-
**Met**
460+
**Met. Warning: Requires lengthier justification.**
461461

462462
Context:
463463
- [CII Best Practices: Security](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#security)
@@ -486,7 +486,7 @@ Context:
486486

487487
> The project results MUST check all inputs from potentially untrusted sources to ensure they are valid (an *allowlist*), and reject invalid inputs, if there are any restrictions on the data at all.
488488
489-
**Met**
489+
**Met. Warning: Requires lengthier justification.**
490490

491491
Context:
492492
- [CII Best Practices: Security](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#security)
@@ -495,7 +495,7 @@ Context:
495495

496496
> Hardening mechanisms SHOULD be used in the software produced by the project so that software defects are less likely to result in security vulnerabilities.
497497
498-
**N/A** The the final user has the power to decide, see: Node.js thread model (https://github.com/nodejs/node/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/SECURITY.md#the-nodejs-threat-model)
498+
**N/A** The the final user has the power to decide, see: Node.js thread model (https://github.com/nodejs/node/blob/main/SECURITY.md#the-nodejs-threat-model)
499499

500500
Context:
501501
- [CII Best Practices: Security](https://github.com/coreinfrastructure/best-practices-badge/blob/a51ed45fdcd8e2959781a86929f561521ac2e0e0/docs/other.md#security)

0 commit comments

Comments
 (0)