Skip to content

[Snyk] Upgrade @balancer/sdk from 0.0.3 to 0.5.0#2

Open
naiba4 wants to merge 1 commit intomainfrom
snyk-upgrade-16adca40107be878d2ab0e32c08f958e
Open

[Snyk] Upgrade @balancer/sdk from 0.0.3 to 0.5.0#2
naiba4 wants to merge 1 commit intomainfrom
snyk-upgrade-16adca40107be878d2ab0e32c08f958e

Conversation

@naiba4
Copy link
Owner

@naiba4 naiba4 commented Jan 24, 2024

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade @balancer/sdk from 0.0.3 to 0.5.0.

ℹ️ 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 10 versions ahead of your current version.
  • The recommended version was released a month ago, on 2023-12-15.
Release notes
Package name: @balancer/sdk
  • 0.5.0 - 2023-12-15

    Minor Changes

    • b8523b1: Add create pool for composable stable pools
    • 43715b5: Add OP native asset and remove unused constant STELLATE_URL

    Patch Changes

    • 1e3ad86: expose priceImpact amount
  • 0.4.0 - 2023-12-12

    Minor Changes

    • e7a8237: Add InitPool functionality for Weighted Pools;
    • 7fff3d9: Add CreatePool functionality for Weighted Pools;
    • d8dc287: Add Price Impact calculations for add/remove liquidity and swaps

    Patch Changes

    • b97bff1: Discard paths with failing limits
  • 0.3.1 - 2023-11-21

    Patch Changes

    • 4eda061: Add Op pools from vulnerability to filter list.
  • 0.3.0 - 2023-11-14

    Minor Changes

    • e1efe6b: - Add add/remove liquidity pool support (non-nested pools)
      • Weighted pool type
      • ComposableStable pool type
      • Uses balancerHelpers to query amounts in/out rather than relying on specific pool math and associated data
      • Integration tests run against local viem fork
    • 73b19fc: Adds Balancer API Provider. A utility module designed to fetch pool data from API.
  • 0.2.0 - 2023-10-12

    Minor Changes

    • f6d1051: Add Fantom config. Update to have network specific vault addr.

    • 67e4120: Replace dataQueries with multicall (using Viem):

      • Add BATCHSIZE config per network
      • Onchain calls correctly mapped to pool/version
      • Filter bricked pools from vulnerability
      • Fix scalingFactor scaling
  • 0.1.2 - 2023-10-12

    Patch Changes

    • 7004561: Add missing gyro3 to SupportedRawPoolTypes.
  • 0.1.1 - 2023-07-24

    Patch Changes

    • ec6fda0: Switched to vitest. Updated viem to fix parseUnits issue
  • 0.1.0 - 2023-07-21

    Minor Changes

    • f04362c: The onChainPoolDataEnricher now also queries the pool rate, linearTargets as well as status of inRecoveryMode and isPaused
  • 0.0.5 - 2023-07-11

    Patch Changes

  • 0.0.4 - 2023-06-24

    Patch Changes

    • 664f0c0: Automate releases with changesets
  • 0.0.3 - 2023-05-19
from @balancer/sdk GitHub release notes

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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@pull-request-quantifier-deprecated

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@guardrails
Copy link

guardrails bot commented Jan 24, 2024

⚠️ We detected 7 security issues in this pull request:

Vulnerable Libraries (7)
Severity Details
Medium pkg:npm/@typescript-eslint/parser@5.46.1 (t) upgrade to: > 5.46.1
High pkg:npm/vuepress@2.0.0-beta.59 (t) upgrade to: > 2.0.0-beta.59
Medium pkg:npm/eslint-plugin-vue@9.8.0 (t) upgrade to: > 9.8.0
Medium pkg:npm/eslint@8.29.0 (t) upgrade to: > 8.29.0
High pkg:npm/vuepress-plugin-md-enhance@2.0.0-beta.143 (t) upgrade to: > 2.0.0-beta.143
High pkg:npm/docsearch.js@2.6.3 (t) upgrade to: > 2.6.3
Medium pkg:npm/@typescript-eslint/eslint-plugin@5.46.1 (t) upgrade to: > 5.46.1

More info on how to fix Vulnerable Libraries in JavaScript.


👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

@socket-security
Copy link

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

Package New capabilities Transitives Size Publisher
npm/@balancer/sdk@0.5.0 Transitive: environment, eval, filesystem, network, unsafe +38 45.2 MB
npm/@sentry/browser@7.95.0 network +7 9.77 MB sentry-bot

🚮 Removed packages: npm/@balancer/sdk@0.0.3, npm/@sentry/browser@7.36.0

View full report↗︎

@socket-security
Copy link

🚨 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 NoteSource
Chronological version anomaly npm/abitype@0.9.8
Chronological version anomaly npm/isows@1.0.3
No contributors or author data npm/isows@1.0.3
No tests npm/isows@1.0.3
Chronological version anomaly npm/typescript@5.3.3
Chronological version anomaly npm/viem@1.21.4
Network access npm/@sentry/utils@7.95.0
Unpublished package npm/@sentry-internal/tracing@7.95.0
  • Version: Invalid Date
Unpublished package npm/@sentry-internal/feedback@7.95.0
  • Version: Invalid Date
Unpublished package npm/@sentry-internal/replay-canvas@7.95.0
  • Version: Invalid Date
Unpublished package npm/@sentry/replay@7.95.0
  • Version: Invalid Date

View full report↗︎

Next steps

What is a chronological version anomaly?

Semantic versions published out of chronological order.

This could either indicate dependency confusion or a patched vulnerability.

Why is contributor and author data important?

Package does not specify a list of contributors or an author in package.json.

Add a author field or contributors array to package.json.

What does no tests mean?

Package does not have any tests. This is a strong signal of a poorly maintained or low quality package.

Add tests and publish a new version of the package. Consumers may look for an alternative package with better testing.

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What are unpublished packages?

Package version was not found on the registry. It may exist on a different registry and need to be configured to pull from that registry.

Packages can be removed from the registry by manually un-publishing, a security issue removal, or may simply never have been published to the registry. Reliance on these packages will cause problem when they are not found.

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 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/abitype@0.9.8
  • @SocketSecurity ignore npm/isows@1.0.3
  • @SocketSecurity ignore npm/typescript@5.3.3
  • @SocketSecurity ignore npm/viem@1.21.4
  • @SocketSecurity ignore npm/@sentry/utils@7.95.0
  • @SocketSecurity ignore npm/@sentry-internal/tracing@7.95.0
  • @SocketSecurity ignore npm/@sentry-internal/feedback@7.95.0
  • @SocketSecurity ignore npm/@sentry-internal/replay-canvas@7.95.0
  • @SocketSecurity ignore npm/@sentry/replay@7.95.0

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants