-
Notifications
You must be signed in to change notification settings - Fork 24
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
Wasm sc integration #1558
Wasm sc integration #1558
Conversation
808386b
to
a010199
Compare
1d4f584
to
0928696
Compare
…undation/archethic-node into wasm_sc_integration
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
14335930 | Triggered | Generic Private Key | 628be5d | test/archethic_web/aeweb/domain_test.exs | 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 secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.
fa4b418
to
92dd4fb
Compare
b12c212
to
966098e
Compare
0266380
to
c48aa5a
Compare
Description
Integrate WASM smart contract execution
Type of change
How Has This Been Tested?
Tested with libjs (archethic-foundation/libjs#222)
Checklist: