Skip to content

[Snyk] Upgrade @vscode/extension-telemetry from 0.8.4 to 0.9.9 - #2

Open
Hardikgosai1 wants to merge 1 commit into
mainfrom
snyk-upgrade-43c230d50e0a8ef62f1d42fa3fc9d15d
Open

[Snyk] Upgrade @vscode/extension-telemetry from 0.8.4 to 0.9.9#2
Hardikgosai1 wants to merge 1 commit into
mainfrom
snyk-upgrade-43c230d50e0a8ef62f1d42fa3fc9d15d

Conversation

@Hardikgosai1

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to upgrade @vscode/extension-telemetry from 0.8.4 to 0.9.9.

ℹ️ 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 11 versions ahead of your current version.

  • The recommended version was released 5 months ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
critical severity Predictable Value Range from Previous Values
SNYK-JS-FORMDATA-10841150
577 Proof of Concept
Release notes
Package name: @vscode/extension-telemetry
  • 0.9.9 - 2025-05-07

    Changes:

    • #224: bump version
    • #223: add node-esm variant
    • #221: Remove extra brace from common.platformversion
    • #220: Bump serialize-javascript and mocha
    • #219: classify new property

    This list of changes was auto generated.

  • 0.9.8 - 2024-11-20

    Changes:

    • #218: Bump version for release
    • #216: Accept instrumentation and connection string
    • #215: Propagate session ID metadata

    This list of changes was auto generated.

  • 0.9.7 - 2024-08-02

    Changes:

    • #213: Bump version + packages
    • #211: Update readme + support connection string
    • #210: Send user id in extension paylod
    • #207: Bump braces from 3.0.2 to 3.0.3
    • #206: Update packages
    • #204: Rollback packages

    This list of changes was auto generated.

  • 0.9.6 - 2024-03-22

    Update packages (#206)

  • 0.9.5 - 2024-03-20

    Rollback packages (#204)

  • 0.9.4 - 2024-03-20
    • Allows measurements to also be undefined for easy omitting, similar to how properties work
  • 0.9.3 - 2024-02-29
    • Improves on the user agent metric shown when navigator.userAgentData is unavailable. Thanks to @ sezna
    • Fixes a bug with telemetry fetching using app insights on older version of node. Thanks to @ devm33
  • 0.9.2 - 2023-12-19

    This release contains a small fix to the 1DS package used by Microsoft extensions in the web to ensure compliance with the California's Global Privacy Control. If you're not a Microsoft extension, then it is safe to disregard this release as it contains no new features or improvements for the third party flow.

  • 0.9.1 - 2023-12-12

    Thanks to a community contribution by @ ilia-db the unhandlederror event handler has been properly fixed to include common properties.

  • 0.9.0 - 2023-11-01

    Application insights web basics comes with the ability to pass in a fetch pollyfill that allows it to be used for both Node and Web. This is similar to what we already do for first party extensions using the 1DS package.

    While there is no breaking changes here, the replacement of a key dependency with what should be an equivalent alternative may have unknown edge cases that were not accounted for, therefore the version has been bumped to reflect this.

    Bundlephobia reports a 67Kb decline in bundle size with this change.

  • 0.8.5 - 2023-09-20
  • 0.8.4 - 2023-08-24
from @vscode/extension-telemetry GitHub release notes

Important

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

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

For more information:

Snyk has created this PR to upgrade @vscode/extension-telemetry from 0.8.4 to 0.9.9.

See this package in npm:
@vscode/extension-telemetry

See this project in Snyk:
https://app.snyk.io/org/hardikgosai1/project/e2e732ee-8311-4865-854d-41a22221abe4?utm_source=github&utm_medium=referral&page=upgrade-pr
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedshortid@​2.2.1610010010081100
Addedsource-map-support@​0.5.2110010010081100
Addedsemver@​7.6.010010010086100
Updated@​vscode/​extension-telemetry@​0.8.4 ⏵ 0.9.9100 +110091 +286 -3100
Addedsinon@​13.0.110010010086100

View full report

@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn Critical
sha.js@2.4.11 has a Critical CVE.

CVE: GHSA-95m3-7q98-8xr5 sha.js is missing type checks leading to hash rewind and passing on crafted data (CRITICAL)

Affected versions: < 2.4.12

Patched version: 2.4.12

From: package-lock.jsonnpm/node-polyfill-webpack-plugin@1.1.4npm/rewiremock@3.14.5npm/sha.js@2.4.11

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: 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@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/sha.js@2.4.11. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants