high:
    - rule:
        cwe_ids:
            - "798"
        id: gitleaks
        title: Hard-coded secret detected.
        description: |
            ## Description

            Hard-coding secrets in a project opens them up to leakage. This rule checks for common secret types such as keys, tokens, and passwords using the popular Gitleaks library and ensures they aren't hard-coded. This rule is part of the secrets scanner and language agnostic.

            ## Remediations

            Do not hard-code secrets in committed code. Instead, use environment variables and a secret management system.

            ## Resources
            - [Gitleaks](https://gitleaks.io/)
        documentation_url: https://docs.bearer.com/reference/rules/gitleaks
      line_number: 3
      full_filename: e2e/rules/testdata/data/secrets/leaked.rb
      filename: leaked.rb
      source:
        location:
            start: 3
            end: 3
            column:
                start: 24
                end: 60
      sink:
        location:
            start: 3
            end: 3
            column:
                start: 24
                end: 60
        content: ""
      parent_line_number: 3
      fingerprint: d0914f16c16550b40063c4f3fb14839e_0
      old_fingerprint: 47146043fab58ba5fc86fd0c716b20d8_0
      detailed_context: PGP private key
      code_extract: '    @private_key ||= ''-----BEGIN PGP PRIVATE KEY BLOCK-----asdf-----END PGP PRIVATE KEY BLOCK-----'''


--
Analyzing codebase

