tests/javascript/express-session-hardcoded-secret-javascript-test.yml (2)

2-8: Enhance valid test case with explicit secure practices

The valid case could be more explicit about proper secret management:

 valid:
   - |
-    let config1 = {
-    secret: config.secret,
+    const sessionConfig = {
+    secret: process.env.SESSION_SECRET,
     resave: false,
     saveUninitialized: false,
     }
+  - |
+    // Using multiple secrets for rotation
+    const sessionConfig = {
+      secret: [
+        process.env.SESSION_SECRET_CURRENT,
+        process.env.SESSION_SECRET_PREVIOUS
+      ],
+      resave: false,
+      saveUninitialized: false
+    }

---

31-31: Add newline at end of file

     saveUninitialized: false,
     }
+

🧰 Tools

🪛 yamllint (1.35.1)

[error] 31-31: no new line character at the end of file

(new-line-at-end-of-file)

tests/javascript/express-jwt-hardcoded-secret-javascript-test.yml (2)

2-7: Enhance valid test cases with additional secure practices

Consider adding more examples of secure JWT configuration:

 valid:
   - |
     app.get('/ok-protected', jwt({ secret: process.env.SECRET }), function(req, res) {
     if (!req.user.admin) return res.sendStatus(401);
     res.sendStatus(200);
     });
+  - |
+    // Using asymmetric key pair
+    const publicKey = fs.readFileSync(process.env.JWT_PUBLIC_KEY_PATH);
+    app.get('/asymmetric-protected', 
+      jwt({ secret: publicKey, algorithms: ['RS256'] }), 
+      function(req, res) {
+        if (!req.user.admin) return res.sendStatus(401);
+        res.sendStatus(200);
+    });
+  - |
+    // Using secret callback for key rotation
+    app.get('/dynamic-protected',
+      jwt({
+        secret: (req, payload, done) => {
+          done(null, process.env.JWT_SECRET);
+        }
+      }),
+      function(req, res) {
+        if (!req.user.admin) return res.sendStatus(401);
+        res.sendStatus(200);
+    });

---

8-44: Add test cases for additional security anti-patterns

Consider adding more invalid cases that demonstrate other security anti-patterns:

 invalid:
   // ... existing cases ...
+  - |
+    // Reading secret from a hardcoded file path
+    const secretFromFile = fs.readFileSync('./jwt-secret.key', 'utf8');
+    app.get('/protected-file', jwt({ secret: secretFromFile }), function(req, res) {
+      if (!req.user.admin) return res.sendStatus(401);
+      res.sendStatus(200);
+    });
+  - |
+    // Using weak secret in development configuration
+    const isDev = process.env.NODE_ENV === 'development';
+    app.get('/protected-dev', 
+      jwt({ secret: isDev ? 'dev-secret' : process.env.SECRET }), 
+      function(req, res) {
+        if (!req.user.admin) return res.sendStatus(401);
+        res.sendStatus(200);
+    });

rules/javascript/security/node-sequelize-hardcoded-secret-argument-javascript.yml (2)

1-13: Consider enhancing the security message with specific remediation steps.

While the message effectively explains the risks, it could be more actionable by including:

• Example of using environment variables
• Reference to specific secret management solutions
• Link to Sequelize's documentation on configuration best practices

 message: >-
   A secret is hard-coded in the application. Secrets stored in source
   code, such as credentials, identifiers, and other types of sensitive data,
   can be leaked and used by internal or external malicious actors. Use
   environment variables to securely provide credentials and other secrets or
   retrieve them from a secure vault or Hardware Security Module (HSM).
+  Example:
+  const sequelize = new Sequelize(process.env.DB_NAME, process.env.DB_USER, process.env.DB_PASS);
+  For production, consider using:
+  - AWS Secrets Manager
+  - HashiCorp Vault
+  - Azure Key Vault

---

73-75: Consider expanding pattern matching for additional security scenarios.

The current rule focuses on basic Sequelize instantiation, but could be enhanced to detect:

• URI connection strings with embedded credentials
• Connection pooling configurations
• SSL certificate paths

Would you like me to provide examples of additional patterns to cover these scenarios?

tests/__snapshots__/node-sequelize-hardcoded-secret-argument-javascript-snapshot.yml (1)

1-109: Enhance test coverage with additional scenarios.

While the current test cases cover basic usage patterns, consider adding:

1. Connection URI strings
2. Environment variable usage (negative test)
3. Configuration objects with nested credentials
4. Connection pool configurations

Would you like me to provide examples of these additional test scenarios?

tests/__snapshots__/express-session-hardcoded-secret-javascript-snapshot.yml (1)

1-270: Consider additional test scenarios for express-session configurations.

While current tests cover basic configurations, consider adding:

1. Environment variable usage (negative test)
2. Complex secret configurations (arrays of secrets)
3. Custom store configurations with embedded credentials
4. Cookie configuration scenarios

Would you like me to provide examples of these additional test scenarios?

rules/javascript/security/express-jwt-hardcoded-secret-javascript.yml (1)

14-143: Consider enhancing MATCH_SECRET_DIRECTLY pattern for additional edge cases.

The pattern effectively catches direct string assignments but could be enhanced to detect:

1. Template literals (e.g., `${secret}`)
2. String concatenation (e.g., 'secret' + process.env.SUFFIX)
3. Object spread syntax (e.g., { ...config, secret: 'value' })

Would you like me to provide the pattern modifications to handle these cases?

🧰 Tools

🪛 yamllint (1.35.1)

[warning] 22-22: wrong indentation: expected 12 but found 11

(indentation)

---

[warning] 25-25: wrong indentation: expected 13 but found 11

(indentation)

---

[warning] 26-26: wrong indentation: expected 15 but found 14

(indentation)

---

[warning] 30-30: wrong indentation: expected 15 but found 14

(indentation)

---

[warning] 33-33: wrong indentation: expected 16 but found 15

(indentation)

---

[warning] 36-36: wrong indentation: expected 17 but found 16

(indentation)

---

[warning] 47-47: wrong indentation: expected 24 but found 26

(indentation)

---

[error] 49-49: trailing spaces

(trailing-spaces)

---

[warning] 55-55: wrong indentation: expected 18 but found 20

(indentation)

---

[warning] 58-58: wrong indentation: expected 22 but found 24

(indentation)

---

[warning] 63-63: wrong indentation: expected 28 but found 30

(indentation)

---

[warning] 66-66: wrong indentation: expected 32 but found 34

(indentation)

---

[warning] 67-67: wrong indentation: expected 38 but found 40

(indentation)

---

[warning] 71-71: wrong indentation: expected 38 but found 40

(indentation)

---

[warning] 74-74: wrong indentation: expected 42 but found 44

(indentation)

---

[warning] 75-75: too many spaces before colon

(colons)

---

[warning] 77-77: wrong indentation: expected 46 but found 48

(indentation)

---

[warning] 84-84: wrong indentation: expected 18 but found 20

(indentation)

---

[warning] 88-88: wrong indentation: expected 26 but found 28

(indentation)

---

[warning] 92-92: wrong indentation: expected 24 but found 26

(indentation)

---

[warning] 99-99: wrong indentation: expected 16 but found 18

(indentation)

---

[warning] 103-103: wrong indentation: expected 24 but found 26

(indentation)

---

[warning] 109-109: wrong indentation: expected 30 but found 32

(indentation)

---

[warning] 113-113: wrong indentation: expected 24 but found 26

(indentation)

---

[warning] 116-116: wrong indentation: expected 28 but found 30

(indentation)

---

[warning] 120-120: wrong indentation: expected 16 but found 18

(indentation)

---

[warning] 127-127: wrong indentation: expected 26 but found 28

(indentation)

---

[warning] 130-130: wrong indentation: expected 30 but found 32

(indentation)

---

[warning] 133-133: wrong indentation: expected 34 but found 36

(indentation)

---

[warning] 137-137: wrong indentation: expected 24 but found 26

(indentation)

rules/javascript/security/express-session-hardcoded-secret-javascript.yml (2)

14-110: Consider additional patterns for MATCH_SECRET utility.

The MATCH_SECRET utility could be enhanced to detect:

1. Environment-based fallbacks (e.g., secret: process.env.SECRET || 'default')
2. Configuration objects (e.g., config.session.secret)

Would you like me to provide the pattern modifications for these cases?

🧰 Tools

🪛 yamllint (1.35.1)

[warning] 23-23: wrong indentation: expected 22 but found 19

(indentation)

---

[warning] 26-26: wrong indentation: expected 23 but found 20

(indentation)

---

[error] 43-43: trailing spaces

(trailing-spaces)

---

[warning] 45-45: wrong indentation: expected 22 but found 20

(indentation)

---

[warning] 49-49: wrong indentation: expected 30 but found 28

(indentation)

---

[warning] 53-53: wrong indentation: expected 38 but found 36

(indentation)

---

[error] 63-63: trailing spaces

(trailing-spaces)

---

[error] 70-70: trailing spaces

(trailing-spaces)

---

[warning] 71-71: wrong indentation: expected 34 but found 32

(indentation)

---

[error] 79-79: trailing spaces

(trailing-spaces)

---

[error] 88-88: trailing spaces

(trailing-spaces)

---

[error] 89-89: trailing spaces

(trailing-spaces)

---

[warning] 97-97: wrong indentation: expected 40 but found 37

(indentation)

---

[error] 109-109: trailing spaces

(trailing-spaces)

---

111-255: Fix YAML indentation for better maintainability.

The file has inconsistent indentation that should be fixed for better maintainability.

Apply this diff to fix the indentation:

     MATCH_SECRET_INSIDE_APP:
         kind: pair
         pattern: $C
         inside:
-            stopBy: end
-            kind: expression_statement
+             stopBy: end
+             kind: expression_statement

🧰 Tools

🪛 yamllint (1.35.1)

[warning] 119-119: wrong indentation: expected 22 but found 19

(indentation)

---

[warning] 122-122: wrong indentation: expected 23 but found 20

(indentation)

---

[warning] 123-123: wrong indentation: expected 26 but found 23

(indentation)

---

[warning] 126-126: wrong indentation: expected 27 but found 23

(indentation)

---

[warning] 127-127: wrong indentation: expected 29 but found 26

(indentation)

---

[warning] 130-130: wrong indentation: expected 29 but found 26

(indentation)

---

[warning] 137-137: wrong indentation: expected 30 but found 28

(indentation)

---

[warning] 141-141: wrong indentation: expected 38 but found 35

(indentation)

---

[warning] 145-145: wrong indentation: expected 38 but found 35

(indentation)

---

[warning] 148-148: wrong indentation: expected 39 but found 36

(indentation)

---

[warning] 152-152: wrong indentation: expected 40 but found 37

(indentation)

---

[warning] 153-153: wrong indentation: expected 43 but found 40

(indentation)

---

[warning] 157-157: wrong indentation: expected 43 but found 44

(indentation)

---

[warning] 158-158: wrong indentation: expected 50 but found 47

(indentation)

---

[warning] 161-161: wrong indentation: expected 50 but found 48

(indentation)

---

[error] 163-163: trailing spaces

(trailing-spaces)

---

[warning] 165-165: wrong indentation: expected 22 but found 20

(indentation)

---

[warning] 169-169: wrong indentation: expected 30 but found 28

(indentation)

---

[warning] 173-173: wrong indentation: expected 38 but found 36

(indentation)

---

[error] 183-183: trailing spaces

(trailing-spaces)

---

[error] 190-190: trailing spaces

(trailing-spaces)

---

[warning] 191-191: wrong indentation: expected 34 but found 32

(indentation)

---

[error] 199-199: trailing spaces

(trailing-spaces)

---

[error] 208-208: trailing spaces

(trailing-spaces)

---

[warning] 210-210: wrong indentation: expected 26 but found 25

(indentation)

---

[warning] 213-213: wrong indentation: expected 29 but found 28

(indentation)

---

[error] 216-216: trailing spaces

(trailing-spaces)

---

[warning] 217-217: wrong indentation: expected 38 but found 35

(indentation)

---

[error] 219-219: trailing spaces

(trailing-spaces)

---

[warning] 220-220: wrong indentation: expected 39 but found 36

(indentation)

---

[error] 226-226: trailing spaces

(trailing-spaces)

---

[warning] 235-235: wrong indentation: expected 40 but found 37

(indentation)

tests/__snapshots__/express-jwt-hardcoded-secret-javascript-snapshot.yml (2)

1-82: Add warning comments for example secrets.

The test cases contain hardcoded secrets that could be mistakenly copied. Consider adding clear warning comments.

Add warning comments like:

+# WARNING: The secrets below are for testing purposes only. Never use hardcoded secrets in production.
 import express from 'express';
 import jwt from 'express-jwt';

---

83-429: Enhance test coverage with negative test cases.

The snapshots focus on detecting hardcoded secrets but could benefit from examples of correct implementations using environment variables or secure configuration patterns.

Would you like me to provide examples of secure configurations to add to the test suite?

Configuration used: CodeRabbit UI
Review profile: CHILL

#!/bin/bash
# Search for Sequelize instantiation patterns that might bypass the rules
echo "Checking Sequelize instantiation patterns..."
rg -t js -t ts "new\s+Sequelize\s*\(" -A 3

# Search for express-session configurations that might bypass the rules
echo "Checking express-session configurations..."
rg -t js -t ts "session\s*\(\s*\{" -A 3

# Search for potential credential string concatenation
echo "Checking string concatenation patterns..."
ast-grep --pattern 'new Sequelize($$$+ $$$)'

#!/bin/bash
# Check the rule definition and test cases
echo "Examining rule definition and test cases..."
fd "express-session.*\.yml" --exec cat {}

# Look for any express-session related test files
echo -e "\nChecking related test files..."
fd "express-session.*\.(js|ts|snap)" --exec cat {}

# Search for session configuration patterns in the entire codebase
echo -e "\nSearching session patterns..."
rg -g "!{dist,node_modules}" "session.*secret"

has:
    stopBy: end
    kind: namespace_import
    has:
        stopBy: end
        kind: identifier
        pattern: $E

#!/bin/bash
# Search for namespace imports of express-jwt in the codebase
ast-grep --pattern $'import * as $E from "express-jwt"'

# Search for potential usage patterns with namespace imports
ast-grep --pattern $'$E.expressJwt({ secret: $_ })'

#!/bin/bash
# Let's try a broader search to find any express-jwt related imports and usage
# Search for any imports of express-jwt
rg -l "express-jwt" --type js --type ts

# Search for any usage of expressJwt or jwt with secret
rg "(?:expressJwt|jwt).*secret" --type js --type ts

# Search for test files that might contain example usage
fd -e test.js -e spec.js -e test.ts -e spec.ts | xargs rg "express-jwt"

#!/bin/bash
# Let's examine the test file to see the actual test cases and usage patterns
cat tests/javascript/express-jwt-hardcoded-secret-javascript-test.yml

# Also check the snapshot file for comprehensive coverage of different import patterns
cat tests/__snapshots__/express-jwt-hardcoded-secret-javascript-snapshot.yml

rules/javascript/security/express-session-hardcoded-secret-javascript.yml (2)

15-110: Add coverage for template literals and string concatenation

The current pattern might miss secrets defined using template literals or string concatenation. Consider adding patterns to catch cases like:

const secret = `my${hardcoded}secret`
// or
const secret = 'my' + 'hardcoded' + 'secret'

Would you like me to help create additional patterns for these cases?

🧰 Tools

🪛 yamllint (1.35.1)

[warning] 23-23: wrong indentation: expected 22 but found 19

(indentation)

---

[warning] 26-26: wrong indentation: expected 23 but found 20

(indentation)

---

[error] 43-43: trailing spaces

(trailing-spaces)

---

[warning] 45-45: wrong indentation: expected 22 but found 20

(indentation)

---

[warning] 49-49: wrong indentation: expected 30 but found 28

(indentation)

---

[warning] 53-53: wrong indentation: expected 38 but found 36

(indentation)

---

[error] 63-63: trailing spaces

(trailing-spaces)

---

[error] 70-70: trailing spaces

(trailing-spaces)

---

[warning] 71-71: wrong indentation: expected 34 but found 32

(indentation)

---

[error] 79-79: trailing spaces

(trailing-spaces)

---

[error] 88-88: trailing spaces

(trailing-spaces)

---

[error] 89-89: trailing spaces

(trailing-spaces)

---

[warning] 97-97: wrong indentation: expected 40 but found 37

(indentation)

---

[error] 109-109: trailing spaces

(trailing-spaces)

---

1-150: Fix YAML formatting issues

The YAML file has several formatting inconsistencies:

1. Inconsistent indentation (e.g., lines 23, 26, 45)
2. Trailing spaces (e.g., lines 43, 63, 70)

Would you like me to provide a properly formatted version of the file?

🧰 Tools

🪛 yamllint (1.35.1)

[warning] 23-23: wrong indentation: expected 22 but found 19

(indentation)

---

[warning] 26-26: wrong indentation: expected 23 but found 20

(indentation)

---

[error] 43-43: trailing spaces

(trailing-spaces)

---

[warning] 45-45: wrong indentation: expected 22 but found 20

(indentation)

---

[warning] 49-49: wrong indentation: expected 30 but found 28

(indentation)

---

[warning] 53-53: wrong indentation: expected 38 but found 36

(indentation)

---

[error] 63-63: trailing spaces

(trailing-spaces)

---

[error] 70-70: trailing spaces

(trailing-spaces)

---

[warning] 71-71: wrong indentation: expected 34 but found 32

(indentation)

---

[error] 79-79: trailing spaces

(trailing-spaces)

---

[error] 88-88: trailing spaces

(trailing-spaces)

---

[error] 89-89: trailing spaces

(trailing-spaces)

---

[warning] 97-97: wrong indentation: expected 40 but found 37

(indentation)

---

[error] 109-109: trailing spaces

(trailing-spaces)

---

[warning] 112-112: wrong indentation: expected 8 but found 6

(indentation)

---

[warning] 126-126: wrong indentation: expected 20 but found 18

(indentation)

---

[warning] 129-129: wrong indentation: expected 22 but found 20

(indentation)

---

[error] 142-142: trailing spaces

(trailing-spaces)

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

-severity: warning
+severity: error

    S:
-        regex: '^secret$'
+        regex: '^(secret|SECRET|sessionSecret|session_secret|jwt_secret|jwtSecret)$'

    S:
        regex: '^(secret|secert|sceret|secret[0-9]|secret_[0-9]|(dev|prod|stage|test)_secret)$'
        ignoreCase: true

#!/bin/bash
# Search for express-session usage patterns in popular repositories
# to ensure our patterns catch real-world scenarios

# Clone top express-session examples
git clone --depth 1 https://github.com/expressjs/session examples/express-session
git clone --depth 1 https://github.com/expressjs/express examples/express

# Search for session secret patterns
echo "Analyzing express-session usage patterns..."
rg -U "session\(.*secret.*\)" examples/ -A 2 -B 2

# Search for potential secret patterns we might miss
echo "Checking for potential missed patterns..."
rg -U "session\(.*\{.*\}.*\)" examples/ -A 2 -B 2

#!/bin/bash
# Let's check for more variations of session configuration

# Check for different import patterns
echo "Checking import patterns..."
rg "import.*session.*express" examples/ -A 2

# Check for different secret assignment patterns
echo "Checking variable assignments..."
rg "const.*secret.*=.*" examples/ -A 2
rg "let.*secret.*=.*" examples/ -A 2

# Check test files for more examples
echo "Checking test files..."
rg -t js "session\(" examples/express-session/test -A 2 -B 2

# Check for environment variable usage patterns
echo "Checking environment variable patterns..."
rg "process\.env\..*SECRET" examples/ -A 2

#!/bin/bash
# Check for CommonJS patterns and session configurations

# Check for require patterns
echo "Checking require patterns..."
rg "require\(['\"]express-session['\"]\)" examples/ -A 3

# Look for session configuration examples in example files
echo "Checking example files..."
fd -e js -e ts -e mjs --exec grep -l "session" {} examples/ | xargs cat

# Check for session middleware setup patterns
echo "Checking middleware patterns..."
rg "app\.use\(.*session" examples/ -A 3 -B 1

rules/javascript/security/express-session-hardcoded-secret-javascript.yml (2)

1-13: ⚠️ Potential issue

Consider upgrading severity to "error"

Hard-coded secrets represent a critical security vulnerability that could lead to credential exposure.

Apply this change:

 id: express-session-hardcoded-secret-javascript
 language: javascript
-severity: warning
+severity: error

---

103-105: 🛠️ Refactor suggestion

Expand secret identifier patterns

The current constraint only matches the exact string "secret".

Apply this change:

     S:
-        regex: '^secret$'
+        regex: '^(secret|SECRET|sessionSecret|session_secret|jwt_secret|jwtSecret)$'

rules/javascript/security/node-sequelize-hardcoded-secret-argument-javascript.yml (1)

85-97: Fix YAML formatting and add missing newline

The file has inconsistent indentation and is missing a newline at the end.

Apply these formatting fixes:

 rule:
-  any:
-     - kind: string
-       matches: MATCH_BLANK_PASSWORD
-     - kind: identifier
-       matches: MATCH_BLANK_PASSWORD_with_instance
+    any:
+        - kind: string
+          matches: MATCH_BLANK_PASSWORD
+        - kind: identifier
+          matches: MATCH_BLANK_PASSWORD_with_instance
 constraints:
-   R:
-    kind: string
-    has:
-       stopBy: neighbor
-       kind: string_fragment
-    
+    R:
+        kind: string
+        has:
+            stopBy: neighbor
+            kind: string_fragment
+

🧰 Tools

🪛 yamllint (1.35.1)

[warning] 86-86: wrong indentation: expected 4 but found 2

(indentation)

---

[warning] 87-87: wrong indentation: expected 6 but found 5

(indentation)

---

[warning] 92-92: wrong indentation: expected 4 but found 3

(indentation)

---

[warning] 93-93: wrong indentation: expected 7 but found 4

(indentation)

---

[warning] 95-95: wrong indentation: expected 8 but found 7

(indentation)

---

[error] 97-97: trailing spaces

(trailing-spaces)

rules/javascript/security/express-jwt-hardcoded-secret-javascript.yml (3)

1-13: Consider enhancing security references

The security message and references are good, but could be strengthened by adding:

• Link to CWE-798 (https://cwe.mitre.org/data/definitions/798.html)
• Reference to NIST guidelines for secret management
• Link to express-jwt security best practices

 note: >-
   [CWE-798] Use of Hard-coded Credentials.
   [REFERENCES]
       - https://cheatsheetseries.owasp.org/cheatsheets/Secrets_Management_Cheat_Sheet.html
+      - https://cwe.mitre.org/data/definitions/798.html
+      - https://auth0.com/blog/express-jwt-security-best-practices/
+      - https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-204C.pdf

---

290-294: Consider additional validation in rule definition

While the rule correctly combines both patterns, consider adding:

1. Pattern validation for environment variables (positive pattern)
2. Maximum string length check for potential secrets
3. Pattern exclusions for test files

 rule:
     kind: pair
+    not:
+      matches: MATCH_ENV_VAR_USAGE
     any:
       - matches: MATCH_SECRET_DIRECTLY
       - matches: MATCH_PATTERN_WITH_INSTANCE
+    where:
+      - pattern: $SECRET
+        maxLength: 100
+    exclude:
+      - "**/*.test.js"
+      - "**/*.spec.js"

🧰 Tools

🪛 yamllint (1.35.1)

[warning] 291-291: wrong indentation: expected 2 but found 4

(indentation)

---

1-294: Fix YAML formatting issues

The file has numerous indentation inconsistencies flagged by yamllint. Consider:

1. Using a consistent 2-space indentation
2. Removing trailing spaces (lines 49, 226)
3. Fixing colon spacing (lines 75, 221)

I can help generate a properly formatted version of the file if needed.

🧰 Tools

🪛 yamllint (1.35.1)

[warning] 22-22: wrong indentation: expected 12 but found 11

(indentation)

---

[warning] 25-25: wrong indentation: expected 13 but found 11

(indentation)

---

[warning] 26-26: wrong indentation: expected 15 but found 14

(indentation)

---

[warning] 30-30: wrong indentation: expected 15 but found 14

(indentation)

---

[warning] 33-33: wrong indentation: expected 16 but found 15

(indentation)

---

[warning] 36-36: wrong indentation: expected 17 but found 16

(indentation)

---

[warning] 47-47: wrong indentation: expected 24 but found 26

(indentation)

---

[error] 49-49: trailing spaces

(trailing-spaces)

---

[warning] 55-55: wrong indentation: expected 18 but found 20

(indentation)

---

[warning] 58-58: wrong indentation: expected 22 but found 24

(indentation)

---

[warning] 63-63: wrong indentation: expected 28 but found 30

(indentation)

---

[warning] 66-66: wrong indentation: expected 32 but found 34

(indentation)

---

[warning] 67-67: wrong indentation: expected 38 but found 40

(indentation)

---

[warning] 71-71: wrong indentation: expected 38 but found 40

(indentation)

---

[warning] 74-74: wrong indentation: expected 42 but found 44

(indentation)

---

[warning] 75-75: too many spaces before colon

(colons)

---

[warning] 77-77: wrong indentation: expected 46 but found 48

(indentation)

---

[warning] 84-84: wrong indentation: expected 18 but found 20

(indentation)

---

[warning] 88-88: wrong indentation: expected 26 but found 28

(indentation)

---

[warning] 92-92: wrong indentation: expected 24 but found 26

(indentation)

---

[warning] 99-99: wrong indentation: expected 16 but found 18

(indentation)

---

[warning] 103-103: wrong indentation: expected 24 but found 26

(indentation)

---

[warning] 109-109: wrong indentation: expected 30 but found 32

(indentation)

---

[warning] 113-113: wrong indentation: expected 24 but found 26

(indentation)

---

[warning] 116-116: wrong indentation: expected 28 but found 30

(indentation)

---

[warning] 120-120: wrong indentation: expected 16 but found 18

(indentation)

---

[warning] 127-127: wrong indentation: expected 26 but found 28

(indentation)

---

[warning] 130-130: wrong indentation: expected 30 but found 32

(indentation)

---

[warning] 133-133: wrong indentation: expected 34 but found 36

(indentation)

---

[warning] 137-137: wrong indentation: expected 24 but found 26

(indentation)

---

[warning] 152-152: wrong indentation: expected 12 but found 11

(indentation)

---

[warning] 155-155: wrong indentation: expected 13 but found 11

(indentation)

---

[warning] 156-156: wrong indentation: expected 15 but found 14

(indentation)

---

[warning] 160-160: wrong indentation: expected 15 but found 14

(indentation)

---

[warning] 163-163: wrong indentation: expected 16 but found 15

(indentation)

---

[warning] 166-166: wrong indentation: expected 17 but found 16

(indentation)

---

[warning] 182-182: wrong indentation: expected 14 but found 16

(indentation)

---

[warning] 185-185: wrong indentation: expected 18 but found 20

(indentation)

---

[warning] 201-201: wrong indentation: expected 18 but found 20

(indentation)

---

[warning] 204-204: wrong indentation: expected 22 but found 24

(indentation)

---

[warning] 209-209: wrong indentation: expected 28 but found 30

(indentation)

---

[warning] 212-212: wrong indentation: expected 32 but found 34

(indentation)

---

[warning] 213-213: wrong indentation: expected 38 but found 40

(indentation)

---

[warning] 217-217: wrong indentation: expected 38 but found 40

(indentation)

---

[warning] 220-220: wrong indentation: expected 42 but found 44

(indentation)

---

[warning] 221-221: too many spaces before colon

(colons)

---

[warning] 223-223: wrong indentation: expected 46 but found 48

(indentation)

---

[error] 226-226: trailing spaces

(trailing-spaces)

---

[warning] 231-231: wrong indentation: expected 18 but found 20

(indentation)

---

[warning] 235-235: wrong indentation: expected 26 but found 28

(indentation)

---

[warning] 239-239: wrong indentation: expected 24 but found 26

(indentation)

---

[warning] 246-246: wrong indentation: expected 16 but found 18

(indentation)

---

[warning] 250-250: wrong indentation: expected 24 but found 26

(indentation)

---

[warning] 256-256: wrong indentation: expected 30 but found 32

(indentation)

---

[warning] 260-260: wrong indentation: expected 24 but found 26

(indentation)

---

[warning] 263-263: wrong indentation: expected 28 but found 30

(indentation)

---

[warning] 267-267: wrong indentation: expected 16 but found 18

(indentation)

---

[warning] 274-274: wrong indentation: expected 26 but found 28

(indentation)

---

[warning] 277-277: wrong indentation: expected 30 but found 32

(indentation)

---

[warning] 280-280: wrong indentation: expected 34 but found 36

(indentation)

---

[warning] 284-284: wrong indentation: expected 24 but found 26

(indentation)

---

[warning] 291-291: wrong indentation: expected 2 but found 4

(indentation)

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro