search

noir-lang / noir-examples

A repo of example Noir projects.
MIT License
40 stars 14 forks source link

moving recursive example to noirjs packages #5

Closed signorecello closed 1 year ago

signorecello commented 1 year ago

As part of NoirJS work, and even though the NoirJS package itself doesn't expose the intermediate stuff, we can still use the backend directly.

For that reason here's a refactor with a working example of recursion on the browser using NoirJS

socket-security[bot] commented 1 year ago

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Packages Version New capabilities Transitives Size Publisher
@noir-lang/noir_js 0.16.0 None +4 7.47 MB noir-lang
@noir-lang/backend_barretenberg 0.7.10 None +3 17.7 MB noir-lang
next 13.5.4 eval, network, filesystem, shell, environment +16 1.1 GB vercel-release-bot
@nomicfoundation/hardhat-toolbox 3.0.0 None +40 31.6 MB fvictorio
@types/mocha 10.0.2 None +0 96.3 kB types
@types/react 18.2.28 None +3 1.6 MB types
@typechain/ethers-v6 0.4.3 network, filesystem +7 18.9 MB ethereum-ts-bot
@nomicfoundation/hardhat-chai-matchers 2.0.2 None +29 29.1 MB fvictorio
@nomicfoundation/hardhat-verify 1.1.1 environment +21 10 MB fvictorio
@nomicfoundation/hardhat-ethers 3.0.4 None +28 28.8 MB fvictorio
@typechain/hardhat 8.0.3 None +28 28.7 MB ethereum-ts-bot
@types/react-dom 18.2.7...18.2.13 None +4/-0 1.63 MB types
@types/node 20.6.0...18.18.4 None +0/-0 3.8 MB types

🚮 Removed packages: @aztec/bb.js@0.7.2, @noir-lang/acvm_js@0.26.1, axios@1.5.0

socket-security[bot] commented 1 year ago

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: next@13.5.4

Next steps

Take a deeper look at the dependency

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.

Remove the package

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.

Mark a package as acceptable risk

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 foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

signorecello commented 1 year ago

@SocketSecurity ignore next@13.5.4