build-with-celo-hackathon
build-with-celo-hackathon copied to clipboard
celo-org
update
⚠️ GitGuardian has uncovered 6 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 | |
|---|---|---|---|---|
| - | Generic Password | a208c31b453ecd12a3192e97e794911305b3124c | PROJECT_NAME/main_page.tsx | View secret |
| - | Generic Password | a208c31b453ecd12a3192e97e794911305b3124c | PROJECT_NAME/main_page.tsx | View secret |
| - | Generic Password | 31c49c6d9162ecd1a8cf328d882c76fbab53c175 | FOW FR/main_page.tsx | View secret |
| - | Generic Password | 31c49c6d9162ecd1a8cf328d882c76fbab53c175 | FOW FR/main_page.tsx | View secret |
| - | Generic High Entropy Secret | 68ceb8cfd493488cf22e64c46f24cb19812447df | FOW FR/fow_client/pages/api/pinata.ts | View secret |
| - | Generic High Entropy Secret | 08d63d743ddd5a7841d0943afaf96534ecd8ab73 | FOW FR/fow_client/pages/api/pinata.ts | 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.
Our GitHub checks need improvements? Share your feedbacks!
![gitguardian[bot] avatar](https://avatars.githubusercontent.com/in/46505?v=4 "Published by a pub.dev verified publisher"){kind=small}
New dependency changes detected. Learn more about Socket for GitHub ↗︎
🚨 Potential security issues found in this pull request. To accept the risk, merge this PR and you will not be notified again.
Bot Commands
To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]
📜 Install scripts
Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.
Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.
🫣 Native code
Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.
Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.
🍣 Git dependency
Contains a dependency which resolves to a remote git URL. Dependencies fetched from git URLs are not immutable can be used to inject untrusted code or reduce the likelihood of a reproducible install.
Publish the git dependency to npm or a private package repository and consume it from there.
| Package | Dependency | Location | Source |
|---|---|---|---|
| [email protected] (added) | ethereumjs-abi@git+https://github.com/ethereumjs/ethereumjs-abi.git | package.json | FOW FR/package-lock.json via @nomiclabs/[email protected], [email protected] |
📞 Telemetry
This package contains telemetry which tracks you.
| Package | Note | Source |
|---|---|---|
| [email protected] (added) | Can be disabled by setting the environment variable NEXT_TELEMETRY_DISABLED=1 | FOW FR/fow_client/package-lock.json, FOW FR/fow_client/package.json |
🧌 Protestware/Troll package
This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.
| Package | Note | Source |
|---|---|---|
| [email protected] (added) | This package prints a protestware console message on install regarding Ukraine for users with Russian language locale | FOW FR/package-lock.json via @nomiclabs/[email protected], [email protected] |
Pull request alert summary
| Issue | Status |
|---|---|
| Install scripts | ⚠️ 5 issues |
| Native code | ⚠️ 10 issues |
| Bin script shell injection | ✅ 0 issues |
| Unresolved require | ✅ 0 issues |
| Invalid package.json | ✅ 0 issues |
| HTTP dependency | ✅ 0 issues |
| Git dependency | ⚠️ 1 issue |
| Potential typo squat | ✅ 0 issues |
| Known Malware | ✅ 0 issues |
| Telemetry | ⚠️ 1 issue |
| Protestware/Troll package | ⚠️ 1 issue |
| AI detected security risk | ✅ 0 issues |
| AI warning | ✅ 0 issues |
📊 Modified Dependency Overview:
![socket-security[bot] avatar](https://avatars.githubusercontent.com/in/156372?v=4 "Published by a pub.dev verified publisher"){kind=small}