-
Notifications
You must be signed in to change notification settings - Fork 182
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
Aptos cli local imports #1244
base: main
Are you sure you want to change the base?
Aptos cli local imports #1244
Conversation
The project can now be built via: ``` pnpm i pnpm clean pnpm build ``` Signed-off-by: Ryan Goulding <goulding@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
…zer on default (#1214) Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: Ryan Goulding <goulding@layerzerolabs.org> Signed-off-by: shankar <shankar@layerzerolabs.org> Co-authored-by: Austin Baltes <abaltes@layerzerolabs.org> Co-authored-by: Matthew Krak <krak@layerzerolabs.org> Co-authored-by: Ryan Goulding <goulding@layerzerolabs.org> Co-authored-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
…1221) Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: shankar <shankar@layerzerolabs.org>
Signed-off-by: Ryan Goulding <goulding@layerzerolabs.org> Signed-off-by: shankar <shankar@layerzerolabs.org> Co-authored-by: Austin Baltes <abaltes@layerzerolabs.org> Co-authored-by: Matthew Krak <krak@layerzerolabs.org> Co-authored-by: Ryan Goulding <goulding@layerzerolabs.org> Co-authored-by: shankar <shankar@layerzerolabs.org>
…s-cli-local-imports
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is unstable ownership?A new collaborator has begun publishing package versions. Package stability and security risk may be elevated. Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm. What are unpopular packages?This package is not very popular. Unpopular packages may have less maintenance and contain other problems. Take a deeper look at the dependencyTake 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 packageIf 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 riskTo ignore an alert, reply with a comment starting with
|
9749c19
to
8c0e51f
Compare
re-doing this because for some reason the changes are gon