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 @docusaurus/plugin-google-gtag from 2.1.0 to 2.4.3 #34

Closed

Conversation

Abuchtela
Copy link
Owner

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


Snyk has created this PR to upgrade @docusaurus/plugin-google-gtag from 2.1.0 to 2.4.3.

ℹ️ 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 6 versions ahead of your current version.
  • The recommended version was released 5 months ago, on 2023-09-20.
Release notes
Package name: @docusaurus/plugin-google-gtag
  • 2.4.3 - 2023-09-20

    2.4.3 (2023-09-20)

    🐛 Bug Fix

    • docusaurus-plugin-content-docs
      • #9107 fix(content-docs): sidebar generator should return customProps for doc items (@ TheCatLady)
    • docusaurus-theme-classic
      • #9108 feat(theme-classic): add description & keywords microdata to blog posts (@ TheCatLady)
      • #9099 fix(theme): only set classname on ul elements if they have an existing class (@ homotechsual)
      • #9243 fix(theme-common): ThemedComponent should display something when JS is disabled (@ slorber)
    • docusaurus-theme-classic, docusaurus-theme-common
      • #9130 fix(theme): canonical url should be not change after hydration if url accessed with/without trailing slash (@ ori-shalom)

    Committers: 4

  • 2.4.1 - 2023-05-15
  • 2.4.0 - 2023-03-23
  • 2.3.1 - 2023-02-03
  • 2.3.0 - 2023-01-27
  • 2.2.0 - 2022-10-29
  • 2.1.0 - 2022-09-02
from @docusaurus/plugin-google-gtag GitHub release notes
Commit messages
Package name: @docusaurus/plugin-google-gtag

Compare


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

Copy link

vercel bot commented Mar 1, 2024

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

Name Status Preview Comments Updated (UTC)
aptos-core ❌ Failed (Inspect) Mar 1, 2024 10:32am
aptos-core-n9hp ❌ Failed (Inspect) Mar 1, 2024 10:32am

Copy link

sonarcloud bot commented Mar 1, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

Copy link

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

Package New capabilities Transitives Size Publisher
npm/mkdirp@1.0.4 environment, filesystem 0 19.1 kB isaacs
npm/path-to-regex@1.3.8 None 0 84.7 kB lastuniverse
npm/prettier@2.7.1 environment, filesystem, unsafe 0 15.8 MB prettier-bot
npm/process@0.11.10 None 0 15.3 kB cwmma
npm/prop-types@15.8.1 environment +4 145 kB ljharb
npm/react@17.0.2 environment +3 318 kB gaearon
npm/rehype-katex@5.0.0 Transitive: environment, filesystem, shell +16 4.67 MB wooorm
npm/remark-math@3.0.1 None 0 19.1 kB wooorm

🚮 Removed packages: npm/@types/jest@28.1.8, npm/dotenv@16.0.2

View full report↗︎

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
Potential typo squat npm/path-to-regex@1.3.8

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

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/path-to-regex@1.3.8

Copy link

This issue is stale because it has been open 45 days with no activity. Remove the stale label, comment or push a commit - otherwise this will be closed in 15 days.

@github-actions github-actions bot added the stale label Apr 16, 2024
@stale stale bot closed this Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants