-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the GMaps API key for APPI #284
Conversation
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
13337747 | Triggered | Google API Key | 955263e | apps/fxc-front/.env.production | View secret |
13337748 | Triggered | Google API Key | 955263e | apps/fxc-front/.env.production | View secret |
13337748 | Triggered | Google API Key | 955263e | apps/fxc-front/.env.production | View secret |
13337749 | Triggered | Google API Key | 955263e | apps/fxc-front/.env.production | View secret |
13337750 | Triggered | Google API Key | 955263e | apps/fxc-front/.env.production | View secret |
13337751 | Triggered | Google API Key | 955263e | apps/fxc-front/.env.production | View secret |
13337751 | Triggered | Google API Key | 955263e | apps/fxc-front/.env.production | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- 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.
🦉 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.
WalkthroughThe recent update enhances the application's environment configuration, introducing API key entries for two new domains, Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
🧙 Sourcery has finished reviewing your pull request! Tips
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @vicb - I've reviewed your changes and found some issues that need to be addressed.
Blocking issues:
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🔴 Security: 2 blocking issues
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.
Deploying flyxc with Cloudflare Pages
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- apps/fxc-front/.env.production (1 hunks)
Additional context used
Gitleaks
apps/fxc-front/.env.production
22-22: Uncovered a GCP API key, which could lead to unauthorized access to Google Cloud services and data breaches.
(gcp-api-key)
23-23: Uncovered a GCP API key, which could lead to unauthorized access to Google Cloud services and data breaches.
(gcp-api-key)
24-24: Uncovered a GCP API key, which could lead to unauthorized access to Google Cloud services and data breaches.
(gcp-api-key)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
package-lock.json
is excluded by!**/package-lock.json
Files selected for processing (2)
- apps/fxc-front/vite.config.mts (2 hunks)
- package.json (7 hunks)
Files skipped from review due to trivial changes (1)
- package.json
Additional comments not posted (3)
apps/fxc-front/vite.config.mts (3)
5-5
: LGTM! The import statement forliteralsHtmlCssMinifier
is correct.The import statement correctly references the
literalsHtmlCssMinifier
package.
5-5
: LGTM! The removal of theminifyHTML
import statement is correct.The removal of the
minifyHTML
import statement is appropriate given the replacement withliteralsHtmlCssMinifier
.
62-62
: LGTM! But verify the compatibility of the new plugin.The replacement of
minifyHTML
withliteralsHtmlCssMinifier
is correct.However, ensure that the new plugin is compatible with the existing configuration and does not introduce any issues during the build process.
Summary by CodeRabbit
New Features
Chores