chore(secret-scan): Failing lint issues

[somya-05]

User description

Description

Fix all the errors during the lint scan.

Fixes #505

Dependencies

None

Future Improvements

Work on all the lint issues while developing the code

Mentions

@rajdip-b

Screenshots of relevant screens

N/A

Developer's checklist

• My PR follows the style guidelines of this project
• I have performed a self-check on my work

If changes are made in the code:

• I have followed the coding guidelines
• My changes in code generate no new warnings
• My changes are breaking another fix/feature of the project
• I have added test cases to show that my feature works
• I have added relevant screenshots in my PR
• There are no UI/UX issues

Documentation Update

• This PR requires an update to the documentation at docs.keyshade.xyz
• I have made the necessary updates to the documentation, or no documentation changes are required.

---

PR Type

Bug fix

---

Description

• Fixed various linting issues across multiple files in the secret-scan package.
• Corrected regex patterns to adhere to linting standards.
• Improved comment formatting for better readability.

---

Changes walkthrough 📝

Relevant files

Bug fix

12 files authress.ts Fix linting issues in Authress regex comments                        packages/secret-scan/src/rules/authress.ts Fixed indentation in comments. Improved readability of the Authress API key regex comment. +3/-3      beamer.ts Fix linting issue in Beamer regex pattern                                packages/secret-scan/src/rules/beamer.ts Corrected regex pattern to fix linting issue. +1/-1      bitbucket.ts Fix linting issue in Bitbucket regex pattern                          packages/secret-scan/src/rules/bitbucket.ts Corrected regex pattern to fix linting issue. +1/-1      cloudflare.ts Fix linting issue in Cloudflare regex pattern                        packages/secret-scan/src/rules/cloudflare.ts Corrected regex pattern to fix linting issue. +1/-1      coinbase.ts Fix linting issue in Coinbase regex pattern                            packages/secret-scan/src/rules/coinbase.ts Corrected regex pattern to fix linting issue. +1/-1      contentful.ts Fix linting issue in Contentful regex pattern                        packages/secret-scan/src/rules/contentful.ts Corrected regex pattern to fix linting issue. +1/-1      definednetworking.ts Fix linting issue in Defined Networking regex pattern        packages/secret-scan/src/rules/definednetworking.ts Corrected regex pattern to fix linting issue. +1/-1      dropbox.ts Fix linting issues in Dropbox regex patterns                          packages/secret-scan/src/rules/dropbox.ts Fixed indentation in comments. Corrected regex pattern to fix linting issue. +3/-3      huggingface.ts Fix linting issue in Huggingface regex pattern                      packages/secret-scan/src/rules/huggingface.ts Corrected regex pattern to fix linting issue. +1/-1      ip_public.ts Fix linting issue in IP Public regex pattern                          packages/secret-scan/src/rules/ip_public.ts Corrected regex pattern to fix linting issue. +1/-1      planetscale.ts Fix linting issue in Planetscale regex patterns                    packages/secret-scan/src/rules/planetscale.ts Corrected regex pattern to fix linting issue. +3/-3      sidekiq.ts Fix linting issue in Sidekiq regex patterns                            packages/secret-scan/src/rules/sidekiq.ts Corrected regex pattern to fix linting issue. +1/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 505 - Fully compliant Fully compliant requirements: Fix linting failures in the secret-scan package Ensure pnpm lint runs without errors

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Regex Modification The regex pattern for Huggingface Organization Access Token has been modified. Verify if the new pattern correctly matches all valid tokens without false positives. Regex Complexity The regex pattern for public IP addresses is complex. Ensure it correctly identifies all public IP addresses without false positives or negatives.

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Maintainability	Use named capture groups in complex regex patterns to improve readability and maintainability Consider using a named capture group for the IP address pattern. This can make the regex more readable and easier to maintain, especially when extracting matches. packages/secret-scan/src/rules/ip_public.ts [7] -/(?<![\w.])((?!(192\.168\.|127\.|10\.|172\.(?:1[6-9]|2[0-9]|3[01])))(?:(?:25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])\.){3}(?:25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])(?::\d{1,5})?)(?![\w.])/ +/(?<![\w.])(?<ip>(?!(192\.168\.|127\.|10\.|172\.(?:1[6-9]|2[0-9]|3[01])))(?:(?:25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])\.){3}(?:25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])(?::\d{1,5})?)(?![\w.])/ Apply this suggestion Suggestion importance[1-10]: 6 Why: Named capture groups can significantly enhance readability and maintainability, especially in complex regex patterns like this one. This suggestion is beneficial for future code maintenance.	6
Performance	Use non-capturing groups in regex patterns to potentially improve performance Consider using a non-capturing group for the character set in the regex pattern. This can slightly improve performance, especially if the regex is used frequently. packages/secret-scan/src/rules/beamer.ts [7] -/b_[a-z0-9=_-]{44}/i +/b_(?:[a-z0-9=_-]{44})/i Apply this suggestion Suggestion importance[1-10]: 5 Why: The suggestion to use non-capturing groups can slightly improve performance, but the impact is minimal given the simplicity of the regex pattern. It is a valid enhancement but not critical.	5
Enhancement	Use non-capturing groups in regex patterns to improve readability and potentially enhance performance Consider using a non-capturing group for the character classes in the regex pattern. This can improve readability and slightly enhance performance. packages/secret-scan/src/rules/huggingface.ts [10] -/(?:^|[\\'"` >=:(,)])(api_org_[a-zA-Z]{34})(?:$|[\\'"` <),])/ +/(?:^|[\\'"` >=:(,)])(?:api_org_[a-zA-Z]{34})(?:$|[\\'"` <),])/ Apply this suggestion Suggestion importance[1-10]: 5 Why: Using non-capturing groups can improve readability and performance slightly. However, the improvement is marginal, and the regex is already quite readable.	5
Best practice	Use template literals for complex regex patterns to enhance readability and maintainability Consider using template literals for the regex pattern to improve readability and maintainability, especially for complex patterns with many escape characters. packages/secret-scan/src/rules/sidekiq.ts [10] -/\bhttps?:\/\/([a-f0-9]{8}:[a-f0-9]{8})@(gems\.contribsys\.com|enterprise\.contribsys\.com)(?:[/|#|?|:]|$)/i +new RegExp(`\\bhttps?://([a-f0-9]{8}:[a-f0-9]{8})@(gems\\.contribsys\\.com|enterprise\\.contribsys\\.com)(?:[/|#|?|:]|$)`, 'i') Apply this suggestion Suggestion importance[1-10]: 4 Why: While using template literals can improve readability, the current regex pattern is not overly complex. The suggestion is valid but offers limited improvement in this context.	4

💡 Need additional feedback ? start a PR chat

[rajdip-b]

🎉 This PR is included in version 2.6.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀