Skip to content
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

[Snyk] Upgrade @sentry/profiling-node from 8.43.0 to 8.47.0 #261

Merged
merged 1 commit into from
Jan 23, 2025

Conversation

snyk-io[bot]
Copy link
Contributor

@snyk-io snyk-io bot commented Jan 23, 2025

snyk-top-banner

Snyk has created this PR to upgrade @sentry/profiling-node from 8.43.0 to 8.47.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 5 versions ahead of your current version.

  • The recommended version was released a month ago.

Release notes
Package name: @sentry/profiling-node
  • 8.47.0 - 2024-12-18
    • feat(v8/core): Add updateSpanName helper function (#14736)
    • feat(v8/node): Do not overwrite prisma db.system in newer Prisma versions (#14772)
    • feat(v8/node/deps): Bump @ prisma/instrumentation from 5.19.1 to 5.22.0 (#14755)
    • feat(v8/replay): Mask srcdoc iframe contents per default (#14779)
    • ref(v8/nextjs): Fix typo in source maps deletion warning (#14776)

    Work in this release was contributed by @ aloisklink and @ benjick. Thank you for your contributions!

    Bundle size 📦

    Path Size
    @ sentry/browser 23.29 KB
    @ sentry/browser - with treeshaking flags 21.96 KB
    @ sentry/browser (incl. Tracing) 35.81 KB
    @ sentry/browser (incl. Tracing, Replay) 73.06 KB
    @ sentry/browser (incl. Tracing, Replay) - with treeshaking flags 63.45 KB
    @ sentry/browser (incl. Tracing, Replay with Canvas) 77.37 KB
    @ sentry/browser (incl. Tracing, Replay, Feedback) 89.85 KB
    @ sentry/browser (incl. Feedback) 40.04 KB
    @ sentry/browser (incl. sendFeedback) 27.89 KB
    @ sentry/browser (incl. FeedbackAsync) 32.68 KB
    @ sentry/react 25.96 KB
    @ sentry/react (incl. Tracing) 38.64 KB
    @ sentry/vue 27.52 KB
    @ sentry/vue (incl. Tracing) 37.67 KB
    @ sentry/svelte 23.45 KB
    CDN Bundle 24.47 KB
    CDN Bundle (incl. Tracing) 37.51 KB
    CDN Bundle (incl. Tracing, Replay) 72.71 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) 78.1 KB
    CDN Bundle - uncompressed 71.85 KB
    CDN Bundle (incl. Tracing) - uncompressed 111.23 KB
    CDN Bundle (incl. Tracing, Replay) - uncompressed 225.3 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 238.52 KB
    @ sentry/nextjs (client) 38.9 KB
    @ sentry/sveltekit (client) 36.32 KB
    @ sentry/node 162.7 KB
    @ sentry/node - without tracing 98.87 KB
    @ sentry/aws-serverless 126.53 KB
  • 8.46.0 - 2024-12-17
    • feat: Allow capture of more than 1 ANR event [v8] (#14713)
    • feat(node): Detect Railway release name [v8] (#14714)
    • fix: Normalise ANR debug image file paths if appRoot was supplied [v8] (#14709)
    • fix(nuxt): Remove build config from tsconfig (#14737)

    Work in this release was contributed by @ conor-ob. Thank you for your contribution!

    Bundle size 📦

    Path Size
    @ sentry/browser 23.29 KB
    @ sentry/browser - with treeshaking flags 21.96 KB
    @ sentry/browser (incl. Tracing) 35.79 KB
    @ sentry/browser (incl. Tracing, Replay) 73.01 KB
    @ sentry/browser (incl. Tracing, Replay) - with treeshaking flags 63.41 KB
    @ sentry/browser (incl. Tracing, Replay with Canvas) 77.32 KB
    @ sentry/browser (incl. Tracing, Replay, Feedback) 89.81 KB
    @ sentry/browser (incl. Feedback) 40.04 KB
    @ sentry/browser (incl. sendFeedback) 27.89 KB
    @ sentry/browser (incl. FeedbackAsync) 32.68 KB
    @ sentry/react 25.96 KB
    @ sentry/react (incl. Tracing) 38.6 KB
    @ sentry/vue 27.49 KB
    @ sentry/vue (incl. Tracing) 37.63 KB
    @ sentry/svelte 23.45 KB
    CDN Bundle 24.43 KB
    CDN Bundle (incl. Tracing) 37.46 KB
    CDN Bundle (incl. Tracing, Replay) 72.64 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) 78.01 KB
    CDN Bundle - uncompressed 71.74 KB
    CDN Bundle (incl. Tracing) - uncompressed 111.05 KB
    CDN Bundle (incl. Tracing, Replay) - uncompressed 225.1 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 238.32 KB
    @ sentry/nextjs (client) 38.88 KB
    @ sentry/sveltekit (client) 36.29 KB
    @ sentry/node 162.53 KB
    @ sentry/node - without tracing 98.72 KB
    @ sentry/aws-serverless 126.4 KB
  • 8.45.1 - 2024-12-16
    • fix(feedback): Return when the sendFeedback promise resolves (#14683)

    Work in this release was contributed by @ antonis. Thank you for your contribution!

    Bundle size 📦

    Path Size
    @ sentry/browser 23.29 KB
    @ sentry/browser - with treeshaking flags 21.96 KB
    @ sentry/browser (incl. Tracing) 35.79 KB
    @ sentry/browser (incl. Tracing, Replay) 73.01 KB
    @ sentry/browser (incl. Tracing, Replay) - with treeshaking flags 63.41 KB
    @ sentry/browser (incl. Tracing, Replay with Canvas) 77.32 KB
    @ sentry/browser (incl. Tracing, Replay, Feedback) 89.81 KB
    @ sentry/browser (incl. Feedback) 40.04 KB
    @ sentry/browser (incl. sendFeedback) 27.89 KB
    @ sentry/browser (incl. FeedbackAsync) 32.68 KB
    @ sentry/react 25.96 KB
    @ sentry/react (incl. Tracing) 38.6 KB
    @ sentry/vue 27.49 KB
    @ sentry/vue (incl. Tracing) 37.63 KB
    @ sentry/svelte 23.45 KB
    CDN Bundle 24.43 KB
    CDN Bundle (incl. Tracing) 37.46 KB
    CDN Bundle (incl. Tracing, Replay) 72.64 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) 78.01 KB
    CDN Bundle - uncompressed 71.74 KB
    CDN Bundle (incl. Tracing) - uncompressed 111.05 KB
    CDN Bundle (incl. Tracing, Replay) - uncompressed 225.1 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 238.32 KB
    @ sentry/nextjs (client) 38.88 KB
    @ sentry/sveltekit (client) 36.29 KB
    @ sentry/node 162.52 KB
    @ sentry/node - without tracing 98.71 KB
    @ sentry/aws-serverless 126.39 KB
  • 8.45.0 - 2024-12-13
    • feat(core): Add handled option to captureConsoleIntegration (#14664)
    • feat(browser): Attach virtual stack traces to HttpClient events (#14515)
    • feat(replay): Upgrade rrweb packages to 2.31.0 (#14689)
    • fix(aws-serverless): Remove v8 layer as it overwrites the current layer for docs (#14679)
    • fix(browser): Mark stack trace from captureMessage with attachStacktrace: true as synthetic (#14668)
    • fix(core): Mark stack trace from captureMessage with attatchStackTrace: true as synthetic (#14670)
    • fix(core): Set level in server runtime captureException (#10587)
    • fix(profiling-node): Guard invocation of native profiling methods (#14676)
    • fix(nuxt): Inline nitro-utils function (#14680)
    • fix(profiling-node): Ensure profileId is added to transaction event (#14681)
    • fix(react): Add React Router Descendant Routes support (#14304)
    • fix: Disable ANR and Local Variables if debugger is enabled via CLI args (#14643)

    Work in this release was contributed by @ anonrig and @ Zih0. Thank you for your contributions!

    Bundle size 📦

    Path Size
    @ sentry/browser 23.29 KB
    @ sentry/browser - with treeshaking flags 21.96 KB
    @ sentry/browser (incl. Tracing) 35.79 KB
    @ sentry/browser (incl. Tracing, Replay) 73.01 KB
    @ sentry/browser (incl. Tracing, Replay) - with treeshaking flags 63.41 KB
    @ sentry/browser (incl. Tracing, Replay with Canvas) 77.32 KB
    @ sentry/browser (incl. Tracing, Replay, Feedback) 89.81 KB
    @ sentry/browser (incl. Feedback) 40.04 KB
    @ sentry/browser (incl. sendFeedback) 27.89 KB
    @ sentry/browser (incl. FeedbackAsync) 32.69 KB
    @ sentry/react 25.96 KB
    @ sentry/react (incl. Tracing) 38.6 KB
    @ sentry/vue 27.49 KB
    @ sentry/vue (incl. Tracing) 37.63 KB
    @ sentry/svelte 23.45 KB
    CDN Bundle 24.43 KB
    CDN Bundle (incl. Tracing) 37.46 KB
    CDN Bundle (incl. Tracing, Replay) 72.64 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) 78.01 KB
    CDN Bundle - uncompressed 71.74 KB
    CDN Bundle (incl. Tracing) - uncompressed 111.05 KB
    CDN Bundle (incl. Tracing, Replay) - uncompressed 225.1 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 238.32 KB
    @ sentry/nextjs (client) 38.89 KB
    @ sentry/sveltekit (client) 36.29 KB
    @ sentry/node 162.52 KB
    @ sentry/node - without tracing 98.71 KB
    @ sentry/aws-serverless 126.38 KB
  • 8.44.0 - 2024-12-12
  • 8.43.0 - 2024-12-10
from @sentry/profiling-node 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 przez Sourcery

Aktualizacja @sentry/profiling-node z wersji 8.43.0 do 8.47.0.

Original summary in English

Summary by Sourcery

Upgrade @sentry/profiling-node from 8.43.0 to 8.47.0.

Snyk has created this PR to upgrade @sentry/profiling-node from 8.43.0 to 8.47.0.

See this package in npm:
@sentry/profiling-node

See this project in Snyk:
https://app.snyk.io/org/reisene/project/55e114f8-489e-4f14-b900-20574b041e59?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr
Copy link

vercel bot commented Jan 23, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
hulaj-dusza-serwis ❌ Failed (Inspect) Jan 23, 2025 7:24am

Copy link
Contributor

aviator-app bot commented Jan 23, 2025

Aviator Changeset actions:

Copy link
Contributor

aviator-app bot commented Jan 23, 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.

Copy link

semanticdiff-com bot commented Jan 23, 2025

Review changes with  SemanticDiff

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

Copy link

Please follow naming conventions! 😿

Copy link
Contributor

coderabbitai bot commented Jan 23, 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.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.

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ąd tego pull requesta. Oto dlaczego:

  • Wygląda na to, że został utworzony przez bota (cześć, snyk-io[bot]!). Zakładamy, że wie, co robi!
  • Wygląda na to, że został utworzony przez bota (znaleziono '[Snyk]' w tytule). Zakładamy, że wie, co robi!
Original comment in English

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot (hey, snyk-io[bot]!). We assume it knows what it's doing!
  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!

Copy link
Contributor Author

snyk-io bot commented Jan 23, 2025

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

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

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.

Code review by ChatGPT

Copy link
Contributor

sourcery-ai bot commented Jan 23, 2025

Przewodnik Recenzenta przez Sourcery

Ten pull request aktualizuje pakiet @sentry/profiling-node z wersji 8.43.0 do 8.47.0. Jest to aktualizacja zależności, a zmiany polegają głównie na zaktualizowaniu wersji pakietu w plikach package.json i package-lock.json.

Brak wygenerowanych diagramów, ponieważ zmiany wydają się proste i nie wymagają wizualnej reprezentacji.

Zmiany na Poziomie Plików

Zmiana Szczegóły Pliki
Zaktualizowano zależność @sentry/profiling-node do wersji 8.47.0.
  • Zmieniono wersję @sentry/profiling-node w package.json z 8.43.0 na 8.47.0.
  • Zaktualizowano wersję @sentry/profiling-node w package-lock.json do 8.47.0.
package.json
package-lock.json

Porady i polecenia

Interakcja z Sourcery

  • Wywołanie nowej recenzji: Skomentuj @sourcery-ai review w pull requeście.
  • Kontynuacja dyskusji: Odpowiedz bezpośrednio na komentarze Sourcery.
  • 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 @sourcery-ai issue, aby utworzyć zgłoszenie.
  • Wygenerowanie tytułu pull requesta: Napisz @sourcery-ai w dowolnym miejscu tytułu pull requesta, aby wygenerować tytuł w dowolnym momencie. Możesz również skomentować @sourcery-ai title w pull requeście, aby (prze-)wygenerować tytuł w dowolnym momencie.
  • Wygenerowanie podsumowania pull requesta: Napisz @sourcery-ai summary w dowolnym miejscu treści pull requesta, aby wygenerować podsumowanie PR dokładnie tam, gdzie chcesz. Możesz również skomentować @sourcery-ai summary w pull requeście, aby (prze-)wygenerować podsumowanie w dowolnym momencie.
  • Wygenerowanie przewodnika recenzenta: Skomentuj @sourcery-ai guide w pull requeście, aby (prze-)wygenerować przewodnik recenzenta w dowolnym momencie.
  • Rozwiązanie wszystkich komentarzy Sourcery: Skomentuj @sourcery-ai resolve w pull requeście, aby rozwiązać wszystkie komentarze Sourcery. Przydatne, jeśli już rozwiązałeś wszystkie komentarze i nie chcesz ich już widzieć.
  • Odrzucenie wszystkich recenzji Sourcery: Skomentuj @sourcery-ai dismiss w pull requeście, 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 wywołać nową recenzję!
  • Wygenerowanie planu działania dla zgłoszenia: Skomentuj @sourcery-ai plan w zgłoszeniu, aby wygenerować plan działania.

Dostosowywanie Twojego Doświadczenia

Uzyskaj dostęp do pulpitu nawigacyjnego, aby:

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

Uzyskiwanie Pomocy

Original review guide in English

Reviewer's Guide by Sourcery

This pull request upgrades the @sentry/profiling-node package from version 8.43.0 to 8.47.0. This is a dependency update, and the changes primarily involve updating the package version in package.json and package-lock.json.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Updated @sentry/profiling-node dependency to version 8.47.0.
  • Changed the version of @sentry/profiling-node in package.json from 8.43.0 to 8.47.0.
  • Updated the version of @sentry/profiling-node in package-lock.json to 8.47.0.
package.json
package-lock.json

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

Copy link

Click here to review and test in web IDE: Contribute

Copy link

Dependency Review

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

OpenSSF Scorecard

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

Scanned Files

  • package-lock.json
  • package.json

Copy link
Contributor

deepsource-io bot commented Jan 23, 2025

Here's the code health analysis summary for commits 46b0963..311862a. 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

mergify bot commented Jan 23, 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

Copy link
Contributor

aviator-app bot commented Jan 23, 2025

Skipping bot pull request creation because the queue is empty and this pull request is up to date with main.

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.

Hi! I'm really happy, that you wanna contribute to my work.

@mergify mergify bot merged commit 0c8f12c into main Jan 23, 2025
34 of 50 checks passed
@mergify mergify bot deleted the snyk-upgrade-08e5976545b00b56618abe3e1ad39755 branch January 23, 2025 07:15
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.

0 participants