Hi @amarpatel, @rvider, @mikeeddington, @nilieskou, @dabeles, @efeller ## Old ~"Community contribution" merge requests These merge requests meet the following criteria: * Open * Labelled ~"Community contribution" and not labelled ~"coach will finish" * Created more than 2 months ago We'd like to ask you to determine whether: * The MR is ready or further changes are required * The MR should be taken over by the team * The MR should be closed down - [ ] gitlab-org/security-products/analyzers/container-scanning!3273 Use of TRIVY_CACHE_DIR as env variable ~"1st contribution", ~"Community contribution", ~"automation:author-reminded", ~"devops::application security testing", ~"group::composition analysis", ~"linked-issue", ~"section::sec", ~"type::bug", ~"workflow::in dev" - [ ] gitlab-org/security-products/analyzers/semgrep!689 Fix typo in README.md for clarity in unit tests section ~"1st contribution", ~"Community contribution", ~"Hackathon", ~"automation:author-reminded", ~"automation:ml", ~"devops::application security testing", ~"documentation", ~"group::static analysis", ~"idle", ~"maintenance::usability", ~"section::sec", ~"type::maintenance", ~"workflow::in dev" For the Merge Requests triaged please check off the box in front of the given MR. Thanks for your help! This report is generated by this [triage-ops policy](https://gitlab.com/gitlab-org/quality/triage-ops/blob/master/policies/groups/gitlab-org/security-products/security-products-community-merge-requests.yml).