From 1e3a99af9adb78159371e232171bf85a96bb070d Mon Sep 17 00:00:00 2001 From: nicklem Date: Thu, 21 Dec 2023 15:47:22 +0100 Subject: [PATCH 1/2] feat: Update the Security category description --- docs/faq/code-analysis/which-metrics-does-codacy-calculate.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq/code-analysis/which-metrics-does-codacy-calculate.md b/docs/faq/code-analysis/which-metrics-does-codacy-calculate.md index 2913b38f22..31b91a6060 100644 --- a/docs/faq/code-analysis/which-metrics-does-codacy-calculate.md +++ b/docs/faq/code-analysis/which-metrics-does-codacy-calculate.md @@ -55,7 +55,7 @@ Codacy calculates the number of issues in the following static code analysis cat - **Performance:** Code that can have performance problems - **Compatibility:** Mainly for frontend code, compatibility problems across different browser versions - **Unused Code:** Unused variables and methods, code that can't be reached -- **Security:** All security problems +- **Security:** Potential security vulnerabilities, including hardcoded passwords and keys (secret scanning), vulnerable dependencies (software composition analysis or SCA), and insecure code patterns (static application security testing or SAST). For more information, see the complete [list of security issue categories](../../repositories/security-monitor.md#supported-security-categories) - **Documentation:** Methods and classes that don't have the correct comment annotations From 300eb6ba9c2c65f135393793b8c465813d518e74 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia=20Carpinteiro?= Date: Tue, 26 Dec 2023 10:34:35 +0000 Subject: [PATCH 2/2] fix: Fix Vale issue --- docs/faq/code-analysis/which-metrics-does-codacy-calculate.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq/code-analysis/which-metrics-does-codacy-calculate.md b/docs/faq/code-analysis/which-metrics-does-codacy-calculate.md index 31b91a6060..adb7455360 100644 --- a/docs/faq/code-analysis/which-metrics-does-codacy-calculate.md +++ b/docs/faq/code-analysis/which-metrics-does-codacy-calculate.md @@ -55,7 +55,7 @@ Codacy calculates the number of issues in the following static code analysis cat - **Performance:** Code that can have performance problems - **Compatibility:** Mainly for frontend code, compatibility problems across different browser versions - **Unused Code:** Unused variables and methods, code that can't be reached -- **Security:** Potential security vulnerabilities, including hardcoded passwords and keys (secret scanning), vulnerable dependencies (software composition analysis or SCA), and insecure code patterns (static application security testing or SAST). For more information, see the complete [list of security issue categories](../../repositories/security-monitor.md#supported-security-categories) +- **Security:** Potential security vulnerabilities, including hard-coded passwords and keys (secret scanning), vulnerable dependencies (software composition analysis or SCA), and insecure code patterns (static application security testing or SAST). For more information, see the complete [list of security issue categories](../../repositories/security-monitor.md#supported-security-categories) - **Documentation:** Methods and classes that don't have the correct comment annotations