Open finoaamukherjee opened 2 months ago
There are 2 topics pending on this PR on which we would appreciate some guidance:
core
package, but the changes we have made in this PR does not include any changes to this package.docs
but that fails in yarn checks. We are not sure why this might be happening. There are 2 topics pending on this PR on which we would appreciate some guidance:
- (Circle) CI pipeline is breaking in a job to compile
core
package, but the changes we have made in this PR does not include any changes to this package.
- Could you provide some guidance on why this might be happening ?
- We have tried to include "@web3-onboard/finoaconnect:1.0.0-alpha.1" as a package in the
docs
but that fails in yarn checks. We are not sure why this might be happening.
- Could you provide some guidance on how to fix this?
Thanks for the PR - I have added a few comments and questions.
Ill checkout the CI pipeline issue.
As for testing the implementation you will use packages/demo, which will need the new module added to the package.json, initialized and added to the demo code. Then you can run yarn && yarn dev
to get the demo started and complete the PR checklist.
Thanks again!
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎
To accept the risk, merge this PR and you will not be notified again.
Alert | Package | Note | Source | CI |
---|---|---|---|---|
Install scripts | npm/protobufjs@6.11.4 |
| 🚫 | |
Install scripts | npm/secp256k1@3.8.0 |
| 🚫 | |
Install scripts | npm/tiny-secp256k1@1.1.6 |
| 🚫 | |
Install scripts | npm/bigint-buffer@1.1.5 |
| 🚫 | |
Install scripts | npm/@sveltejs/kit@1.30.4 |
| 🚫 | |
Install scripts | npm/svelte-preprocess@5.1.4 |
| 🚫 |
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.
Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.
If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.
To ignore an alert, reply with a comment starting with @SocketSecurity ignore
followed by a space separated list of ecosystem/package-name@version
specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0
or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore npm/protobufjs@6.11.4
@SocketSecurity ignore npm/secp256k1@3.8.0
@SocketSecurity ignore npm/tiny-secp256k1@1.1.6
@SocketSecurity ignore npm/bigint-buffer@1.1.5
@SocketSecurity ignore npm/@sveltejs/kit@1.30.4
@SocketSecurity ignore npm/svelte-preprocess@5.1.4
There are 2 topics pending on this PR on which we would appreciate some guidance:
- (Circle) CI pipeline is breaking in a job to compile
core
package, but the changes we have made in this PR does not include any changes to this package.
- Could you provide some guidance on why this might be happening ?
- We have tried to include "@web3-onboard/finoaconnect:1.0.0-alpha.1" as a package in the
docs
but that fails in yarn checks. We are not sure why this might be happening.
- Could you provide some guidance on how to fix this?
Thanks for the PR - I have added a few comments and questions.
Ill checkout the CI pipeline issue. As for testing the implementation you will use packages/demo, which will need the new module added to the package.json, initialized and added to the demo code. Then you can run
yarn && yarn dev
to get the demo started and complete the PR checklist.Thanks again!
The checks for sanity are now completed in the PR, except the one for CI pipelines. The dApp on localhost boots up fine, but does not enlist the FinoaConnect option yet. I will work to checkout why this is happening.
The PR has now been updated to return error code 4200 (UNSUPPORTED_METHOD) for all method calls that are not supported by FinoaConnect provider.
@finoaamukherjee Im still seeing build errors - https://github.com/blocknative/web3-onboard/actions/runs/9503906496/job/26195385651?pr=2188
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@antfu/utils@0.7.8, npm/@babel/helper-define-polyfill-provider@0.6.2, npm/@babel/plugin-transform-runtime@7.24.7, npm/@lit-labs/ssr-dom-shim@1.2.0, npm/@lit/reactive-element@1.6.3, npm/@motionone/animation@10.17.0, npm/@motionone/dom@10.17.0, npm/@motionone/types@10.17.0, npm/@motionone/utils@10.17.0, npm/@nodelib/fs.stat@2.0.5, npm/@protobufjs/aspromise@1.1.2
Description
Integration of FinoaConnect (Finoa's Wallet Connector Service) into Web3Onboard for distribution through BlockNative. For any questions or queries, please reach out to:
PLEASE NOTE- Checklist must be complete prior to review.
Checklist
package.json
of the package you have made changes in following semantic versioning and using alpha release taggingyarn check-all
to confirm there are not any associated errorsDocs Checklist
docs/package.json
file (if applicable)If this PR includes changes to add an injected wallet or SDK wallet module:
Please complete the following using the internal demo package. To run this demo use the command
yarn && yarn dev
to get the project running athttp://localhost:8080/
[Finoa] It was verified that Finoa's documentation appears underdocs
. TheFinoaConnect
option does show up on the list of injected wallets, and we have verified that connecting and disconnecting the wallet to the dApp works fine.Tests with demo app (injected)
Tests with demo app (SDK)
Screenshots
Screenshot of FinoaConnect under
docs