Skip to content

Conversation

@reisene
Copy link
Owner

@reisene reisene commented Apr 11, 2025

reisene Powered by Pull Request Badge

snyk-top-banner

Snyk has created this PR to upgrade @sentry/browser from 9.6.1 to 9.7.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 2 versions ahead of your current version.

  • The recommended version was released 22 days ago.

Release notes
Package name: @sentry/browser
  • 9.7.0 - 2025-03-20
    • feat(core): Add captureLog method (#15717)
    • feat(remix/cloudflare): Export sentryHandleError (#15726)
    • fix(node): Always flush on Vercel before Lambda freeze (#15602)
    • fix(node): Ensure incoming traces are propagated without HttpInstrumentation (#15732)
    • fix(node): Use fatal level for unhandled rejections in strict mode (#15720)
    • fix(nuxt): Delete Nuxt server template injection (#15749)

    Bundle size 📦

    Path Size
    @ sentry/browser 23.28 KB
    @ sentry/browser - with treeshaking flags 23.09 KB
    @ sentry/browser (incl. Tracing) 36.33 KB
    @ sentry/browser (incl. Tracing, Replay) 73.5 KB
    @ sentry/browser (incl. Tracing, Replay) - with treeshaking flags 66.93 KB
    @ sentry/browser (incl. Tracing, Replay with Canvas) 78.13 KB
    @ sentry/browser (incl. Tracing, Replay, Feedback) 90.69 KB
    @ sentry/browser (incl. Feedback) 40.42 KB
    @ sentry/browser (incl. sendFeedback) 27.91 KB
    @ sentry/browser (incl. FeedbackAsync) 32.7 KB
    @ sentry/react 25.08 KB
    @ sentry/react (incl. Tracing) 38.23 KB
    @ sentry/vue 27.52 KB
    @ sentry/vue (incl. Tracing) 38.02 KB
    @ sentry/svelte 23.3 KB
    CDN Bundle 24.49 KB
    CDN Bundle (incl. Tracing) 36.37 KB
    CDN Bundle (incl. Tracing, Replay) 71.39 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) 76.57 KB
    CDN Bundle - uncompressed 71.56 KB
    CDN Bundle (incl. Tracing) - uncompressed 107.94 KB
    CDN Bundle (incl. Tracing, Replay) - uncompressed 219.2 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 231.77 KB
    @ sentry/nextjs (client) 39.52 KB
    @ sentry/sveltekit (client) 36.73 KB
    @ sentry/node 142.62 KB
    @ sentry/node - without tracing 96.01 KB
    @ sentry/aws-serverless 120.37 KB
  • 9.7.0-alpha.0 - 2025-03-19

    This is an alpha release that includes experimental features which are subject to breaking changes.

    • fix(node): Ensure httpIntegration propagates traces #15735
    • feat(browser): Attach top-level domain to "Failed to fetch" errors #15729

    Bundle size 📦

    Path Size
    @ sentry/browser 23.26 KB
    @ sentry/browser - with treeshaking flags 23.07 KB
    @ sentry/browser (incl. Tracing) 36.32 KB
    @ sentry/browser (incl. Tracing, Replay) 73.5 KB
    @ sentry/browser (incl. Tracing, Replay) - with treeshaking flags 66.92 KB
    @ sentry/browser (incl. Tracing, Replay with Canvas) 78.13 KB
    @ sentry/browser (incl. Tracing, Replay, Feedback) 90.68 KB
    @ sentry/browser (incl. Feedback) 40.4 KB
    @ sentry/browser (incl. sendFeedback) 27.9 KB
    @ sentry/browser (incl. FeedbackAsync) 32.68 KB
    @ sentry/react 25.07 KB
    @ sentry/react (incl. Tracing) 38.21 KB
    @ sentry/vue 27.51 KB
    @ sentry/vue (incl. Tracing) 38.01 KB
    @ sentry/svelte 23.29 KB
    CDN Bundle 24.48 KB
    CDN Bundle (incl. Tracing) 36.36 KB
    CDN Bundle (incl. Tracing, Replay) 71.38 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) 76.56 KB
    CDN Bundle - uncompressed 71.45 KB
    CDN Bundle (incl. Tracing) - uncompressed 107.83 KB
    CDN Bundle (incl. Tracing, Replay) - uncompressed 219.09 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 231.66 KB
    @ sentry/nextjs (client) 39.48 KB
    @ sentry/sveltekit (client) 36.72 KB
    @ sentry/node 142.8 KB
    @ sentry/node - without tracing 96.15 KB
    @ sentry/aws-serverless 120.54 KB
  • 9.6.1 - 2025-03-19
    • feat(deps): bump @ prisma/instrumentation from 6.4.1 to 6.5.0 (#15714)
    • feat(deps): bump @ sentry/cli from 2.42.2 to 2.42.3 (#15711)
    • fix(nextjs): Re-patch router if it is overridden by Next.js (#15721)
    • fix(nuxt): Add Nitro Rollup plugin to inject Sentry server config (#15710)
    • chore(deps): Bump rollup to 4.35.0 (#15651)

    Bundle size 📦

    Path Size
    @ sentry/browser 23.15 KB
    @ sentry/browser - with treeshaking flags 22.94 KB
    @ sentry/browser (incl. Tracing) 36.21 KB
    @ sentry/browser (incl. Tracing, Replay) 73.39 KB
    @ sentry/browser (incl. Tracing, Replay) - with treeshaking flags 66.81 KB
    @ sentry/browser (incl. Tracing, Replay with Canvas) 78.01 KB
    @ sentry/browser (incl. Tracing, Replay, Feedback) 90.57 KB
    @ sentry/browser (incl. Feedback) 40.3 KB
    @ sentry/browser (incl. sendFeedback) 27.79 KB
    @ sentry/browser (incl. FeedbackAsync) 32.58 KB
    @ sentry/react 24.97 KB
    @ sentry/react (incl. Tracing) 38.1 KB
    @ sentry/vue 27.4 KB
    @ sentry/vue (incl. Tracing) 37.9 KB
    @ sentry/svelte 23.18 KB
    CDN Bundle 24.36 KB
    CDN Bundle (incl. Tracing) 36.26 KB
    CDN Bundle (incl. Tracing, Replay) 71.27 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) 76.45 KB
    CDN Bundle - uncompressed 71.19 KB
    CDN Bundle (incl. Tracing) - uncompressed 107.57 KB
    CDN Bundle (incl. Tracing, Replay) - uncompressed 218.83 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 231.39 KB
    @ sentry/nextjs (client) 39.38 KB
    @ sentry/sveltekit (client) 36.63 KB
    @ sentry/node 142.29 KB
    @ sentry/node - without tracing 95.71 KB
    @ sentry/aws-serverless 120.06 KB
from @sentry/browser 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.

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:

Podsumowanie od Sourcery

Aktualizacja zależności @sentry/browser z wersji 9.6.1 do 9.7.0

Nowe funkcje:

  • Dodano metodę captureLog
  • Eksport sentryHandleError dla Remix/Cloudflare

Poprawki błędów:

  • Naprawiono obsługę nieobsłużonych odrzuceń w trybie ścisłym
  • Zapewniono propagację przychodzących śladów (traces)
  • Naprawiono wstrzykiwanie szablonu serwera Nuxt
Original summary in English

Summary by Sourcery

Upgrade @sentry/browser dependency from version 9.6.1 to 9.7.0

New Features:

  • Add captureLog method
  • Export sentryHandleError for Remix/Cloudflare

Bug Fixes:

  • Fix unhandled rejections handling in strict mode
  • Ensure incoming traces are propagated
  • Fix Nuxt server template injection

Snyk has created this PR to upgrade @sentry/browser from 9.6.1 to 9.7.0.

See this package in npm:
@sentry/browser

See this project in Snyk:
https://app.snyk.io/org/reisene/project/3b48baaa-833b-4239-b348-16091472ee83?utm_source=github&utm_medium=referral&page=upgrade-pr
@aviator-app
Copy link
Contributor

aviator-app bot commented Apr 11, 2025

Aviator Changeset actions:

@aviator-app
Copy link
Contributor

aviator-app bot commented Apr 11, 2025

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This PR was merged manually (without Aviator). Merging manually can negatively impact the performance of the queue. Consider using Aviator next time.


See the real-time status of this PR on the Aviator webapp.
Use the Aviator Chrome Extension to see the status of your PR within GitHub.

@semanticdiff-com
Copy link

semanticdiff-com bot commented Apr 11, 2025

Review changes with  SemanticDiff

Changed Files
File Status
  package-lock.json  65% smaller
  package.json  0% smaller

@naming-conventions-bot
Copy link

Please follow naming conventions! 😿

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 11, 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.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions
Copy link

Click here to review and test in web IDE: Contribute

@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Apr 11, 2025

🧙 Sourcery zakończył przegląd Twojego pull requesta!


Porady i polecenia

Interakcja z Sourcery

  • Uruchomienie nowej recenzji: Skomentuj @sourcery-ai review w pull requestcie.
  • Kontynuowanie dyskusji: Odpowiadaj bezpośrednio na komentarze Sourcery dotyczące recenzji.
  • Wygenerowanie zgłoszenia GitHub z komentarza recenzji: Poproś Sourcery o utworzenie
    zgłoszenia z komentarza recenzji, odpowiadając na niego. Możesz również odpowiedzieć na
    komentarz recenzji za pomocą @sourcery-ai issue, aby utworzyć z niego zgłoszenie.
  • Wygenerowanie tytułu pull requesta: Napisz @sourcery-ai w dowolnym miejscu w tytule
    pull requesta, aby wygenerować tytuł w dowolnym momencie. Możesz również skomentować
    @sourcery-ai title w pull requestcie, aby (ponownie) wygenerować tytuł w dowolnym momencie.
  • Wygenerowanie podsumowania pull requesta: Napisz @sourcery-ai summary w dowolnym miejscu
    w treści pull requesta, aby wygenerować podsumowanie PR w dowolnym momencie, dokładnie tam,
    gdzie chcesz. Możesz również skomentować @sourcery-ai summary w pull requestcie, aby
    (ponownie) wygenerować podsumowanie w dowolnym momencie.
  • Wygenerowanie przewodnika recenzenta: Skomentuj @sourcery-ai guide w pull requestcie,
    aby (ponownie) wygenerować przewodnik recenzenta w dowolnym momencie.
  • Rozwiązanie wszystkich komentarzy Sourcery: Skomentuj @sourcery-ai resolve w pull
    requestcie, aby rozwiązać wszystkie komentarze Sourcery. Przydatne, jeśli wszystkie
    komentarze zostały już uwzględnione i nie chcesz ich więcej widzieć.
  • Odrzucenie wszystkich recenzji Sourcery: Skomentuj @sourcery-ai dismiss w pull
    requestcie, aby odrzucić wszystkie istniejące recenzje Sourcery. Szczególnie przydatne,
    jeśli chcesz zacząć od nowa z nową recenzją - nie zapomnij skomentować
    @sourcery-ai review, aby uruchomić nową recenzję!
  • Wygenerowanie planu działania dla zgłoszenia: Skomentuj @sourcery-ai plan w zgłoszeniu,
    aby wygenerować plan działania dla niego.

Dostosowywanie Twojego doświadczenia

Uzyskaj dostęp do swojego panelu, aby:

  • Włączyć lub wyłączyć funkcje recenzji, takie jak podsumowanie pull requesta
    wygenerowane przez Sourcery, przewodnik recenzenta i inne.
  • Zmienić język recenzji.
  • Dodawać, usuwać lub edytować niestandardowe instrukcje recenzji.
  • Dostosować inne ustawienia recenzji.

Uzyskiwanie pomocy

Original review guide in English

🧙 Sourcery has finished reviewing your pull request!


Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@github-actions
Copy link

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails
npm/@sentry-internal/browser-utils 9.7.0 🟢 5
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 27 issue activity found in the last 90 days -- score normalized to 10
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
License🟢 10license file detected
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Branch-Protection⚠️ 1branch protection is not maximal on development and all release branches
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 061 existing vulnerabilities detected
npm/@sentry-internal/feedback 9.7.0 🟢 5
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 27 issue activity found in the last 90 days -- score normalized to 10
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
License🟢 10license file detected
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Branch-Protection⚠️ 1branch protection is not maximal on development and all release branches
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 061 existing vulnerabilities detected
npm/@sentry-internal/replay 9.7.0 🟢 5
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 27 issue activity found in the last 90 days -- score normalized to 10
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
License🟢 10license file detected
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Branch-Protection⚠️ 1branch protection is not maximal on development and all release branches
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 061 existing vulnerabilities detected
npm/@sentry-internal/replay-canvas 9.7.0 🟢 5
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 27 issue activity found in the last 90 days -- score normalized to 10
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
License🟢 10license file detected
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Branch-Protection⚠️ 1branch protection is not maximal on development and all release branches
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 061 existing vulnerabilities detected
npm/@sentry/browser 9.7.0 🟢 5
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 27 issue activity found in the last 90 days -- score normalized to 10
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
License🟢 10license file detected
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Branch-Protection⚠️ 1branch protection is not maximal on development and all release branches
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 061 existing vulnerabilities detected
npm/@sentry/core 9.7.0 🟢 5
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 27 issue activity found in the last 90 days -- score normalized to 10
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
License🟢 10license file detected
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Branch-Protection⚠️ 1branch protection is not maximal on development and all release branches
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 061 existing vulnerabilities detected
npm/@sentry/browser ^9.7.0 🟢 5
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 27 issue activity found in the last 90 days -- score normalized to 10
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
License🟢 10license file detected
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Branch-Protection⚠️ 1branch protection is not maximal on development and all release branches
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 061 existing vulnerabilities detected

Scanned Files

  • package-lock.json
  • package.json

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@deepsource-io
Copy link
Contributor

deepsource-io bot commented Apr 11, 2025

Here's the code health analysis summary for commits 68f5dbe..3bb4114. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource JavaScript LogoJavaScript✅ SuccessView Check ↗
DeepSource PHP LogoPHP✅ SuccessView Check ↗
DeepSource Test coverage LogoTest coverage⚠️ Artifact not reportedTimed out: Artifact was never reportedView Check ↗

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Pominęliśmy przeglądanie tego żądaniaPull Request. Wygląda na to, że zostało ono utworzone przez bota (w tytule znaleziono '[Snyk]'). Zakładamy, że wie, co robi!

Original comment in English

We have skipped reviewing this pull request. It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!

@mergify
Copy link
Contributor

mergify bot commented Apr 11, 2025

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Do not merge outdated PRs

Wonderful, this rule succeeded.

Make sure PRs are almost up to date before merging

  • #commits-behind <= 10

@sonarqubecloud
Copy link

@snyk-io
Copy link
Contributor

snyk-io bot commented Apr 11, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

@mergify mergify bot merged commit a8ae5d7 into main Apr 11, 2025
33 of 49 checks passed
@mergify mergify bot deleted the snyk-upgrade-a4dedec39b6020853cd740ad8443c685 branch April 11, 2025 09:33
@github-actions github-actions bot restored the snyk-upgrade-a4dedec39b6020853cd740ad8443c685 branch April 11, 2025 09:33
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.

3 participants