Create 122

[itsarraj0test]

AppSec Wiki Pull Request

Change Description:

Changes Made:

Reason for Change:

Checklist:

• I have tested the changes locally
• Is Code changes ready for review
• I have proofread the changes to ensure accuracy
• I have tested any links or references within the wiki page
• I have checked for consistency with other existing pages (if applicable)
• I have updated any relevant cross-references or documentation

[github-actions]

Hey @itsarraj0test 👋, Thanks for contributing the new Pull Request !!

Secrets Bot

🔎 Detected hardcoded secrets in your pull request

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials

SCA Bot

All good in the hood no vulnerable package found in raised Pull-Request. Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.