Skip to content

[Snyk] Upgrade @permaweb/aoconnect from 0.0.78 to 0.0.90#3

Open
Dustin4444 wants to merge 1 commit into
mainfrom
snyk-upgrade-f3b77ef3822aa5157cf8980a7ec0fbe4
Open

[Snyk] Upgrade @permaweb/aoconnect from 0.0.78 to 0.0.90#3
Dustin4444 wants to merge 1 commit into
mainfrom
snyk-upgrade-f3b77ef3822aa5157cf8980a7ec0fbe4

Conversation

@Dustin4444
Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to upgrade @permaweb/aoconnect from 0.0.78 to 0.0.90.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 12 versions ahead of your current version.

  • The recommended version was released a month ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577916
562 Proof of Concept
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577917
562 Proof of Concept
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577918
562 Proof of Concept
high severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-8172694
562 No Known Exploit
critical severity Information Exposure
SNYK-JS-ELLIPTIC-8720086
562 Proof of Concept
high severity Improper Validation of Integrity Check Value
SNYK-JS-SECP256K1-8237220
562 Proof of Concept
high severity Denial of Service (DoS)
SNYK-JS-WS-7266574
562 Proof of Concept
Release notes
Package name: @permaweb/aoconnect
  • 0.0.90 - 2025-08-21

    chore(connect): release 0.0.90

  • 0.0.89 - 2025-08-11

    chore(connect): release 0.0.89

  • 0.0.88 - 2025-08-08

    chore(connect): release 0.0.88

  • 0.0.87 - 2025-08-06

    chore(connect): release 0.0.87

  • 0.0.86 - 2025-08-04

    chore(connect): release 0.0.86

  • 0.0.85 - 2025-05-21

    chore(connect): release 0.0.85

  • 0.0.84 - 2025-05-10
  • 0.0.83 - 2025-05-08
  • 0.0.82 - 2025-04-16
  • 0.0.81 - 2025-04-16
  • 0.0.80 - 2025-04-16
  • 0.0.79 - 2025-04-10
  • 0.0.78 - 2025-04-02
from @permaweb/aoconnect GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @permaweb/aoconnect from 0.0.78 to 0.0.90.

See this package in npm:
@permaweb/aoconnect

See this project in Snyk:
https://app.snyk.io/org/dustin4444/project/2607ba15-0c64-4775-9c4a-fd42079dd4b9?utm_source=github&utm_medium=referral&page=upgrade-pr
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @Dustin4444, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates a crucial security update, upgrading the @permaweb/aoconnect package to its latest stable version. The primary goal is to mitigate several critical and high-severity vulnerabilities identified in its transitive dependencies, thereby enhancing the overall security posture of the application. This proactive update ensures the project benefits from the latest security patches and improvements.

Highlights

  • Dependency Upgrade: The @permaweb/aoconnect dependency has been upgraded from version 0.0.78 to 0.0.90.
  • Security Fixes: This upgrade resolves multiple critical and high-severity vulnerabilities, including issues related to cryptographic signature verification, information exposure, integrity check validation, and denial of service in underlying dependencies like elliptic, secp256k1, and ws.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Oct 5, 2025

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch snyk-upgrade-f3b77ef3822aa5157cf8980a7ec0fbe4

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request upgrades the @permaweb/aoconnect dependency to address several security vulnerabilities. The update in create-ao-dapp/templates/apps/lua-sqlite/package.json is correct. However, the review identified that the same dependency in another template file, create-ao-dapp/templates/apps/lua/package.json, was not updated, leaving the project exposed to the same security risks. A critical comment has been added to highlight this issue.

"@arweave-wallet-kit/wander-strategy": "^0.1.2",
"@arweave-wallet-kit/webwallet-strategy": "0.0.1-beta.4",
"@permaweb/aoconnect": "^0.0.78",
"@permaweb/aoconnect": "^0.0.90",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

While this dependency upgrade is correct and important for security, the same dependency in create-ao-dapp/templates/apps/lua/package.json is still at the vulnerable version ^0.0.78. This is a critical oversight that leaves a security vulnerability in your project. Please update the dependency in that file as well to fully resolve the security issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants