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

build(deps): Bump @sentry/profiling-node from 8.54.0 to 9.0.0 #278

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 10, 2025

dependabot[bot] Contributor Powered by Pull Request Badge

Bumps @sentry/profiling-node from 8.54.0 to 9.0.0.

Release notes

Sourced from @​sentry/profiling-node's releases.

9.0.0-alpha.2

This is an alpha release of the upcoming major release of version 9. This release does not yet entail a comprehensive changelog as version 9 is not yet stable.

For this release's iteration of the migration guide, see the Migration Guide as per 9.0.0-alpha.2. Please note that the migration guide is work in progress and subject to change.

Bundle size 📦

Path Size
@​sentry/browser 22.9 KB
@​sentry/browser - with treeshaking flags 22.69 KB
@​sentry/browser (incl. Tracing) 35.77 KB
@​sentry/browser (incl. Tracing, Replay) 72.58 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 66.05 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 76.82 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 89.56 KB
@​sentry/browser (incl. Feedback) 39.84 KB
@​sentry/browser (incl. sendFeedback) 27.53 KB
@​sentry/browser (incl. FeedbackAsync) 32.31 KB
@​sentry/react 24.73 KB
@​sentry/react (incl. Tracing) 37.66 KB
@​sentry/vue 27.09 KB
@​sentry/vue (incl. Tracing) 37.47 KB
@​sentry/svelte 22.94 KB
CDN Bundle 24.13 KB
CDN Bundle (incl. Tracing) 35.84 KB
CDN Bundle (incl. Tracing, Replay) 70.48 KB
CDN Bundle (incl. Tracing, Replay, Feedback) 75.62 KB
CDN Bundle - uncompressed 70.58 KB
CDN Bundle (incl. Tracing) - uncompressed 106.46 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed 217.31 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 229.88 KB
@​sentry/nextjs (client) 38.63 KB
@​sentry/sveltekit (client) 36.2 KB
@​sentry/node 156.58 KB
@​sentry/node - without tracing 97.58 KB
@​sentry/aws-serverless 107.07 KB

9.0.0-alpha.1

This is an alpha release of the upcoming major release of version 9. This release does not yet entail a comprehensive changelog as version 9 is not yet stable.

For this release's iteration of the migration guide, see the Migration Guide as per 9.0.0-alpha.1. Please note that the migration guide is work in progress and subject to change.

Bundle size 📦

| Path | Size |

... (truncated)

Changelog

Sourced from @​sentry/profiling-node's changelog.

9.0.0

Version 9.0.0 marks a release of the Sentry JavaScript SDKs that contains breaking changes. The goal of this release is to trim down on unused and potentially confusing APIs, prepare the SDKs for future framework versions to build deeper instrumentation, and remove old polyfills to reduce the packages' size.

How To Upgrade

Please carefully read through the migration guide in the Sentry docs on how to upgrade from version 8 to version 9. Make sure to select your specific platform/framework in the top left corner: https://docs.sentry.io/platforms/javascript/migration/v8-to-v9/

A comprehensive migration guide outlining all changes for all the frameworks can be found within the Sentry JavaScript SDK Repository: https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md

Breaking Changes

  • doc(deno)!: Make Deno v2 the minimum supported version (#15085)
  • feat!: Bump typescript to ~5.0.0 (#14758)
  • feat!: Drop nitro-utils package (#14998)
  • feat!: Only collect ip addresses with sendDefaultPii: true (#15084)
  • feat!: Remove autoSessionTracking option (#14802)
  • feat!: Remove enableTracing (#15078)
  • feat!: Remove getCurrentHub(), Hub, and getCurrentHubShim() (#15122)
  • feat!: Remove spanId from propagation context (#14733)
  • feat!: Remove deprecated and unused code (#15077)
  • feat!: Remove metrics API from the JS SDK (#14745)
  • feat!: Require Node >=18 as minimum supported version (#14749)
  • feat(astro)!: Respect user-specified source map setting (#14941)
  • feat(browser)!: Remove captureUserFeedback method (#14820)
  • feat(build)!: Drop pre-ES2020 polyfills (#14882)
  • feat(core)!: Add normalizedRequest to samplingContext (#14902)
  • feat(core)!: Always use session from isolation scope (#14860)
  • feat(core)!: Pass root spans to beforeSendSpan and disallow returning null (#14831)
  • feat(core)!: Remove BAGGAGE_HEADER_NAME export (#14785)
  • feat(core)!: Remove TransactionNamingScheme type (#14865)
  • feat(core)!: Remove addOpenTelemetryInstrumentation method (#14792)
  • feat(core)!: Remove arrayify method (#14782)
  • feat(core)!: Remove debugIntegration and sessionTimingIntegration (#14747)
  • feat(core)!: Remove flatten method (#14784)
  • feat(core)!: Remove getDomElement method (#14797)
  • feat(core)!: Remove makeFifoCache method (#14786)
  • feat(core)!: Remove memoBuilder export & WeakSet fallback (#14859)
  • feat(core)!: Remove transactionContext from samplingContext (#14904)
  • feat(core)!: Remove urlEncode method (#14783)
  • feat(core)!: Remove deprecated Request type (#14858)
  • feat(core)!: Remove deprecated request data methods (#14896)
  • feat(core)!: Remove standalone Client interface & deprecate BaseClient (#14800)
  • feat(core)!: Remove validSeverityLevels export (#14765)
  • feat(core)!: Stop accepting event as argument for recordDroppedEvent (#14999)
  • feat(core)!: Stop setting user in requestDataIntegration (#14898)
  • feat(core)!: Type sdkProcessingMetadata more strictly (#14855)
  • feat(core)!: Update hasTracingEnabled to consider empty trace config (#14857)

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Podsumowanie od Sourcery

Build:

  • Podniesiono wersję @sentry/profiling-node z 8.54.0 do 9.0.0.
Original summary in English

Summary by Sourcery

Build:

  • Bump @sentry/profiling-node from 8.54.0 to 9.0.0.

Bumps [@sentry/profiling-node](https://github.com/getsentry/sentry-javascript) from 8.54.0 to 9.0.0.
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md)
- [Commits](https://github.com/getsentry/sentry-javascript/commits)

---
updated-dependencies:
- dependency-name: "@sentry/profiling-node"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 10, 2025
Copy link
Contributor

aviator-app bot commented Feb 10, 2025

Aviator Changeset actions:

Copy link
Contributor

aviator-app bot commented Feb 10, 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 using Aviator.


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 Feb 10, 2025

Review changes with  SemanticDiff

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

Copy link

Please follow naming conventions! 😿

Copy link
Contributor

coderabbitai bot commented Feb 10, 2025

Important

Review skipped

Bot user detected.

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

Click here to review and test in web IDE: Contribute

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 (hej, dependabot[bot]!). 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 (hey, dependabot[bot]!). We assume it knows what it's doing!

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.

Auto approved automated PR

Copy link
Contributor

sourcery-ai bot commented Feb 10, 2025

Przewodnik Recenzenta od Sourcery

PR podnosi zależność @sentry/profiling-node z wersji ^8.54.0 do ^9.0.0, aktualizując pliki package.json i package-lock.json. Ta zmiana aktualizuje zależność do nowej głównej wersji, która zawiera zmiany powodujące niezgodność wsteczną i wymaga przestrzegania wytycznych migracji Sentry.

Nie wygenerowano żadnych diagramów, ponieważ zmiany wydają się proste i nie wymagają wizualnej reprezentacji.

Zmiany na Poziomie Pliku

Zmiana Szczegóły Pliki
Zaktualizowano wersję zależności @sentry/profiling-node.
  • Zmodyfikowano package.json, aby zmienić wersję z ^8.54.0 na ^9.0.0.
  • Przeliczono package-lock.json, aby odzwierciedlić zaktualizowaną zależność i jej zależności przechodnie.
package.json
package-lock.json

Porady i polecenia

Interakcja z Sourcery

  • Uruchom nową recenzję: Skomentuj @sourcery-ai review w żądaniu pull request.
  • Kontynuuj dyskusje: Odpowiadaj bezpośrednio na komentarze recenzji Sourcery.
  • Wygeneruj zgłoszenie 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.
  • Wygeneruj tytuł żądania pull request: Napisz @sourcery-ai w dowolnym miejscu w
    tytule żądania pull request, aby wygenerować tytuł w dowolnym momencie. Możesz również skomentować
    @sourcery-ai title w żądaniu pull request, aby (ponownie) wygenerować tytuł w dowolnym momencie.
  • Wygeneruj podsumowanie żądania pull request: Napisz @sourcery-ai summary w dowolnym miejscu w
    treści żądania pull request, aby wygenerować podsumowanie PR w dowolnym momencie, dokładnie tam, gdzie
    chcesz. Możesz również skomentować @sourcery-ai summary w żądaniu pull request, aby
    (ponownie) wygenerować podsumowanie w dowolnym momencie.
  • Wygeneruj przewodnik recenzenta: Skomentuj @sourcery-ai guide w żądaniu pull
    request, aby (ponownie) wygenerować przewodnik recenzenta w dowolnym momencie.
  • Rozwiąż wszystkie komentarze Sourcery: Skomentuj @sourcery-ai resolve w żądaniu
    pull request, aby rozwiązać wszystkie komentarze Sourcery. Przydatne, jeśli już
    odniosłeś się do wszystkich komentarzy i nie chcesz ich więcej widzieć.
  • Odrzuć wszystkie recenzje Sourcery: Skomentuj @sourcery-ai dismiss w żądaniu
    pull request, 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ę!
  • Wygeneruj plan działania dla zgłoszenia: Skomentuj @sourcery-ai plan w
    zgłoszeniu, aby wygenerować plan działania dla niego.

Dostosowywanie Doświadczenia

Uzyskaj dostęp do swojego panelu, aby:

  • Włączyć lub wyłączyć funkcje recenzji, takie jak podsumowanie żądania pull request 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

Reviewer's Guide by Sourcery

The PR bumps the @sentry/profiling-node dependency from version ^8.54.0 to ^9.0.0, updating both the package.json and package-lock.json files. This change updates the dependency to a new major version which includes breaking changes and requires following Sentry's migration guidelines.

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

File-Level Changes

Change Details Files
Updated the @sentry/profiling-node dependency version.
  • Modified package.json to change the version from ^8.54.0 to ^9.0.0.
  • Recomputed package-lock.json to reflect the updated dependency and its transitive dependencies.
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

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

Copy link
Contributor

snyk-io bot commented Feb 10, 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

Dependency Review

The following issues were found:
  • ✅ 0 vulnerable package(s)
  • ✅ 0 package(s) with incompatible licenses
  • ✅ 0 package(s) with invalid SPDX license definitions
  • ⚠️ 1 package(s) with unknown licenses.
See the Details below.

License Issues

package-lock.json

PackageVersionLicenseIssue Type
@sentry-internal/node-cpu-profiler2.0.0NullUnknown License

OpenSSF Scorecard

Scorecard details
PackageVersionScoreDetails
npm/@opentelemetry/api-logs 0.56.0 🟢 6
Details
CheckScoreReason
Maintained🟢 1030 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
Code-Review🟢 10all changesets reviewed
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not 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
Binary-Artifacts🟢 10no binaries found in the repo
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
Security-Policy🟢 10security policy file detected
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Pinned-Dependencies🟢 3dependency not pinned by hash detected -- score normalized to 3
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 10SAST tool is run on all commits
Vulnerabilities⚠️ 28 existing vulnerabilities detected
npm/@opentelemetry/instrumentation 0.56.0 🟢 6
Details
CheckScoreReason
Maintained🟢 1030 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
Code-Review🟢 10all changesets reviewed
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not 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
Binary-Artifacts🟢 10no binaries found in the repo
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
Security-Policy🟢 10security policy file detected
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Pinned-Dependencies🟢 3dependency not pinned by hash detected -- score normalized to 3
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 10SAST tool is run on all commits
Vulnerabilities⚠️ 28 existing vulnerabilities detected
npm/@prisma/instrumentation 6.2.1 🟢 6.6
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Security-Policy🟢 9security policy file detected
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Packaging⚠️ -1packaging workflow not detected
License🟢 10license file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ -1internal error: error during GetBranch(6.2.x): error during branchesHandler.query: internal error: githubv4.Query: Resource not accessible by integration
Binary-Artifacts🟢 10no binaries found in the repo
Fuzzing🟢 10project is fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Vulnerabilities⚠️ 030 existing vulnerabilities detected
npm/@sentry-internal/node-cpu-profiler 2.0.0 UnknownUnknown
npm/@sentry/core 9.0.0 🟢 5.2
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
License🟢 10license file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Security-Policy🟢 10security policy file detected
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.
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 045 existing vulnerabilities detected
npm/@sentry/node 9.0.0 🟢 5.2
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
License🟢 10license file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Security-Policy🟢 10security policy file detected
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.
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 045 existing vulnerabilities detected
npm/@sentry/opentelemetry 9.0.0 🟢 5.2
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
License🟢 10license file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Security-Policy🟢 10security policy file detected
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.
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 045 existing vulnerabilities detected
npm/@sentry/profiling-node 9.0.0 🟢 5.2
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
License🟢 10license file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Security-Policy🟢 10security policy file detected
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.
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 045 existing vulnerabilities detected
npm/import-in-the-middle 1.13.0 UnknownUnknown
npm/node-abi 3.74.0 UnknownUnknown
npm/semver 7.7.1 🟢 7.2
Details
CheckScoreReason
Maintained🟢 109 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Packaging⚠️ -1packaging workflow not detected
Code-Review🟢 10all changesets reviewed
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Binary-Artifacts🟢 10no binaries found in the repo
Security-Policy🟢 10security policy file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Vulnerabilities🟢 100 existing vulnerabilities detected
License🟢 10license file detected
Fuzzing⚠️ 0project is not fuzzed
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
SAST🟢 9SAST tool detected but not run on all commits
npm/@sentry/profiling-node ^9.0.0 🟢 5.2
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
License🟢 10license file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Security-Policy🟢 10security policy file detected
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.
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 045 existing vulnerabilities detected

Scanned Files

  • package-lock.json
  • package.json

Copy link
Contributor

aviator-app bot commented Feb 10, 2025

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

Copy link
Contributor

deepsource-io bot commented Feb 10, 2025

Here's the code health analysis summary for commits 8c1ff0d..d5f26a4. 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 Feb 10, 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

@aviator-app aviator-app bot merged commit b5074d1 into main Feb 10, 2025
33 of 53 checks passed
@aviator-app aviator-app bot deleted the dependabot/npm_and_yarn/sentry/profiling-node-9.0.0 branch February 10, 2025 12:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AnyChange dependencies Pull requests that update a dependency file release root size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants