RPCScan script

[shraddha761]

Description

Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.

Fixes #504

Replace issue_no with the issue number which is fixed in this PR

Have you read the Contributing Guidelines on Pull Requests?

• Yes
• No

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Documentation Update

Checklist:

• My code follows the style guidelines(Clean Code) of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I've edited the SCRIPTS.md and link to my code.
• I have created a helpful and easy to understand README.md
• My documentation follows Template for README.md
• My changes generate no new warnings
• I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your 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.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
-	Google API Key	b50ec99	Phising-Website/PhishFinity/sites/instafollowers/login_files/analytics.js	View secret
-	Google API Key	b50ec99	Phising-Website/PhishFinity/sites/instafollowers/login_files/analytics.js	View secret

🛠 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
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>