Skip to content
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

Ft friday demo #5

Closed
wants to merge 18 commits into from
Closed

Ft friday demo #5

wants to merge 18 commits into from

Conversation

sevelinCa
Copy link
Contributor

No description provided.

Lapidis2 and others added 12 commits May 13, 2024 00:50
installs node dependencies, builds source code and runs tests for continuous integration
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
Copy link

gitguardian bot commented May 17, 2024

⚠️ GitGuardian has uncovered 8 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 GitGuardian status Secret Commit Filename
11039936 Triggered Username Password 5b07d08 src/database/config/config.js View secret
11039936 Triggered Username Password 35b05a5 src/database/config/config.js View secret
11050043 Triggered PostgreSQL Credentials 59d3c01 .env View secret
11050043 Triggered PostgreSQL Credentials 59d3c01 .env View secret
11050043 Triggered PostgreSQL Credentials 59d3c01 .env View secret
11050043 Triggered PostgreSQL Credentials 050d9be .env View secret
11050043 Triggered PostgreSQL Credentials 050d9be .env View secret
11050043 Triggered PostgreSQL Credentials 050d9be .env 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


🦉 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.

berniceu and others added 6 commits May 17, 2024 14:15
…merce-crafters-bn into ft-friday-demo

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
@sevelinCa sevelinCa closed this May 17, 2024
@sevelinCa sevelinCa deleted the ft-friday-demo branch May 17, 2024 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants