+| Recognised open-source security baseline, third tier | The same criteria at the **gold** level | https://www.bestpractices.dev/projects/14772 | **Not held; 30% when this row was first written, before the tree work below landed.** Met in the tree: `require_2FA` (the organisation enforces two-factor authentication for write access); `copyright_per_file` and `license_per_file`, held by `test/spdx_headers_test.exs`; `code_review_standards`, the *Code review* section of docs/03-conventions.md; `small_tasks`, the *Good first tasks* section of CONTRIBUTING.md; `security_review`, docs/11-security-review.md dated 2026-09-23 with five resolved findings and four open; `build_reproducible`, **met for the release** and re-runnable with `./scripts/check_reproducible.sh` (all 243 modules this project compiles are byte-identical across two builds from a clean tree; three dependency modules and the per-release secret cookie are not, and are named). **Not applicable:** `test_branch_coverage80`, because the criterion is conditional on a FLOSS tool existing for the language and `cover:analyse/3` raises `function_clause` for `branch`, which is what every Elixir coverage tool wraps. **Outstanding, not glossed:** `bus_factor`, `contributors_unassociated` and `two_person_review` all need people other than the author in the git history and cannot be bought with code; `test_statement_coverage90` needs 90% against the current 80.31%; `dynamic_analysis` and `dynamic_analysis_enable_assertions` need a tool the project does not run; `secure_2FA` depends on which second factor the maintainers use | maintainer |
0 commit comments