[Snyk] Upgrade jose from 5.9.6 to 6.0.4

[snyk-io]

Snyk has created this PR to upgrade jose from 5.9.6 to 6.0.4.

ℹ️ 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.

---

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

• The recommended version is 6 versions ahead of your current version.

• The recommended version was released 22 days ago.

Release notes

Package name: jose

• 6.0.4 - 2025-02-22
  

  Refactor

  • optimize base64 with tc39/proposal-arraybuffer-base64 (8a0da69), closes #752
  • update getSPKI to use crypto.createPublicKey when available (92392a0), closes #752
  • use Double HMAC pattern for AES-CBC tag comparison (f3ba4c7), closes #752
• 6.0.3 - 2025-02-22
  

  Documentation

  • remove root module tag so that README.md shows up on jsr.io (ee70698)
• 6.0.2 - 2025-02-22
  

  Documentation

  • add module tags to all entrypoints (a5687aa)
• 6.0.1 - 2025-02-22
  

  Fixes

  • types: update build to include extensions in type imports (9b96672)
• 6.0.0 - 2025-02-22
  

  ⚠ BREAKING CHANGES

  • The PEMImportOptions type interface is renamed to KeyImportOptions.
  • all builds and bundles now use ES2022 as target
  • createRemoteJWKSet now uses fetch, because of that its Node.js only options.agent property has been removed and new fetch-related options were added
  • drop support for Ed448 and X448
  • drop support for JWK key_ops and CryptoKey usages "(un)wrapKey" and "deriveKey"
  • resolved keys returned as part of verify/decrypt operations (when get key functions are used) are always normalized to either Uint8Array / CryptoKey depending on what's more efficient for the executed operation
  • Key "Type" Generics are removed
  • CJS-style require is now only possible when require(esm) support is present in the Node.js runtime
  • private KeyObject instances can no longer be used for verify operations
  • private KeyObject instances can no longer be used for encryption operations
  • generateSecret, generateKeyPair, importPKCS8, importSPKI, importJWK, and importX509 now yield a CryptoKey instead of a KeyObject in Node.js
  • drop support for Node.js 18.x and earlier
  • runtime-specific npm releases (jose-browser-runtime, jose-node-cjs-runtime, and jose-node-esm-runtime) are no longer maintained or supported
  • removed secp256k1 JWS support
  • removed deprecated experimental APIs
  • removed RSA1_5 JWE support

  Features

  • enable CryptoKey and KeyObject inputs in JWK thumbprint functions (6fc9c44)
  • JSON Web Key is now an allowed input everywhere (ebda967)

  Refactor

  • always use infered CryptoKey (c4abaa2)
  • backport the Ed25519 JWS Algorithm Identifier support (7a94cb9)
  • drop support for Ed448 and X448 (2fae1c4)
  • drop support for JWK key_ops and CryptoKey usages "(un)wrapKey" and "deriveKey" (ef918be)
  • ensure export functions continue to work with KeyObject inputs (28e9e68)
  • hardcode the cryptoRuntime export since it is now always WebCryptoAPI (e00f273)
  • JWK import extractable default for public keys is now true (64dcebe)
  • PEM import extractable default for public keys is now true (4e9f114)
  • removed deprecated APIs (5352083)
  • removed secp256k1 JWS support (e2b58a5)
  • restructure src/lib and src/runtime now that runtime is fixed (9b236ce)
  • target is now ES2022 everywhere (aa590d5)
  • update importJWK args to align with other import functions (355a2dd)
  • WebCryptoAPI is now the only crypto used (161de46)
• 5.10.0 - 2025-02-17
  

  Features

  • support fully specified Ed25519 algorithm identifier (c39f57d)
• 5.9.6 - 2024-10-20
  

  Reverts

  • Revert "refactor(build): simplify package exports" (2ef3a52)

from jose GitHub release notes

---

Important

• Warning: This PR contains a major version upgrade, and may be a breaking change.
• 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:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by Sourcery

Build:

• Update the jose dependency from version 5.9.6 to 6.0.4.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request upgrades the jose dependency from version 5.9.6 to 6.0.4. This includes updating the version in both 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
The pull request upgrades the jose dependency from version 5.9.6 to 6.0.4.	Updated the jose dependency version in package.json. Updated the jose dependency version in package-lock.json.	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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

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!