build-with-celo-hackathon
build-with-celo-hackathon copied to clipboard
celo-org
RUN3 Submission
Socket Security Pull Request Report
Dependency issues detected. If you merge this pull request, you will not be alerted to the instances of these issues again.
📜 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.
😵💫 Bin script confusion
This package has multiple bin scripts with the same name. This can cause non-deterministic behavior when installing or could be a sign of a supply chain attack
Consider removing one of the conflicting packages. Packages should only export bin scripts with their name
| Package | Bin script | Source |
|---|---|---|
| @nomicfoundation/[email protected] (added) | rlp |
RUN3/package.json via [email protected] |
| [email protected] (added) | rlp |
RUN3/package.json via @nomiclabs/[email protected], [email protected], @ethereum-waffle/[email protected], [email protected], [email protected] |
| [email protected] (added) | rlp |
RUN3/package.json via [email protected], @metamask/[email protected], [email protected] |
🧌 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 | RUN3/package.json via @nomiclabs/[email protected], [email protected], @ethereum-waffle/[email protected], [email protected], [email protected] |
Pull request report summary
| Issue | Status |
|---|---|
| Install scripts | ⚠️ 17 issues |
| Native code | ⚠️ 5 issues |
| Bin script confusion | ⚠️ 3 issues |
| Bin script shell injection | ✅ 0 issues |
| Unresolved require | ✅ 0 issues |
| Invalid package.json | ✅ 0 issues |
| HTTP dependency | ✅ 0 issues |
| Git dependency | ✅ 0 issues |
| Potential typo squat | ✅ 0 issues |
| Known Malware | ✅ 0 issues |
| Telemetry | ✅ 0 issues |
| Protestware/Troll package | ⚠️ 1 issue |
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] [email protected]
@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]
Powered by socket.dev
![socket-security[bot] avatar](https://avatars.githubusercontent.com/in/156372?v=4 "Published by a pub.dev verified publisher"){kind=small}
⚠️ GitGuardian has uncovered 4 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 | aad9c0596c96c1afc044f33059e1f33446567334 | RUN3/app.json | View secret |
| - | Google API Key | ea067a7e15808188c2ca3bcf0fc1ac85fe2dbb88 | RUN3/app.json | View secret |
| - | Google API Key | a4c586e6191cce173c65f620bff56237147fce65 | RUN3/app.json | View secret |
| - | Google API Key | 9a81052a9a98ee11c511b9ef3664101b3c4a9b17 | RUN3/app.json | 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}