Skip to content

Bump the microsoftextensions group with 6 updates#148

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/nuget/microsoftextensions-82ea01a849
Open

Bump the microsoftextensions group with 6 updates#148
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/nuget/microsoftextensions-82ea01a849

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Feb 16, 2026

Updated Microsoft.Extensions.ApiDescription.Server from 10.0.0 to 10.0.3.

Release notes

Sourced from Microsoft.Extensions.ApiDescription.Server's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Http from 9.0.0 to 10.0.3.

Release notes

Sourced from Microsoft.Extensions.Http's releases.

10.0.0-preview.6.25358.103

You can build .NET 10.0 Preview 6 from the repository by cloning the release tag v10.0.0-preview.6.25358.103 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.5.25277.114

You can build .NET 10.0 Preview 5 from the repository by cloning the release tag v10.0.0-preview.5.25277.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.4.25258.110

You can build .NET 10.0 Preview 4 from the repository by cloning the release tag v10.0.0-preview.4.25258.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.3.25171.5

You can build .NET 10.0 Preview 3 from the repository by cloning the release tag v10.0.0-preview.3.25171.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.2.25163.2

You can build .NET 10.0 Preview 2 from the repository by cloning the release tag v10.0.0-preview.2.25163.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.1.25080.5

You can build .NET 10.0 Preview 1 from the repository by cloning the release tag v10.0.0-preview.1.25080.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.114

You can build .NET 9.0 from the repository by cloning the release tag v9.0.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.113

You can build .NET 9.0 from the repository by cloning the release tag v9.0.113 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.112

You can build .NET 9.0 from the repository by cloning the release tag v9.0.112 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.111

You can build .NET 9.0 from the repository by cloning the release tag v9.0.111 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.110

You can build .NET 9.0 from the repository by cloning the release tag v9.0.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.109

You can build .NET 9.0 from the repository by cloning the release tag v9.0.109 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.101

You can build .NET 9.0 from the repository by cloning the release tag v9.0.101 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.7

You can build .NET 9.0 from the repository by cloning the release tag v9.0.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.6

You can build .NET 9.0 from the repository by cloning the release tag v9.0.6 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.5

You can build .NET 9.0 from the repository by cloning the release tag v9.0.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.4

You can build .NET 9.0 from the repository by cloning the release tag v9.0.4 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.3

You can build .NET 9.0 from the repository by cloning the release tag v9.0.3 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.2

You can build .NET 9.0 from the repository by cloning the release tag v9.0.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.1

You can build .NET 9.0 from the repository by cloning the release tag v9.0.1 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

Commits viewable in compare view.

Updated Microsoft.Extensions.Http.Resilience from 10.0.0 to 10.3.0.

Release notes

Sourced from Microsoft.Extensions.Http.Resilience's releases.

10.3.0

What's Changed

New Contributors

... (truncated)

10.2.0

What's Changed

New Contributors

Full Changelog: dotnet/extensions@v10.1...v10.2.0

10.1.0

What's Changed

Commits viewable in compare view.

Updated Microsoft.Extensions.Logging.Debug from 9.0.0 to 10.0.3.

Release notes

Sourced from Microsoft.Extensions.Logging.Debug's releases.

10.0.0-preview.6.25358.103

You can build .NET 10.0 Preview 6 from the repository by cloning the release tag v10.0.0-preview.6.25358.103 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.5.25277.114

You can build .NET 10.0 Preview 5 from the repository by cloning the release tag v10.0.0-preview.5.25277.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.4.25258.110

You can build .NET 10.0 Preview 4 from the repository by cloning the release tag v10.0.0-preview.4.25258.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.3.25171.5

You can build .NET 10.0 Preview 3 from the repository by cloning the release tag v10.0.0-preview.3.25171.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.2.25163.2

You can build .NET 10.0 Preview 2 from the repository by cloning the release tag v10.0.0-preview.2.25163.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.1.25080.5

You can build .NET 10.0 Preview 1 from the repository by cloning the release tag v10.0.0-preview.1.25080.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.114

You can build .NET 9.0 from the repository by cloning the release tag v9.0.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.113

You can build .NET 9.0 from the repository by cloning the release tag v9.0.113 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.112

You can build .NET 9.0 from the repository by cloning the release tag v9.0.112 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.111

You can build .NET 9.0 from the repository by cloning the release tag v9.0.111 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.110

You can build .NET 9.0 from the repository by cloning the release tag v9.0.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.109

You can build .NET 9.0 from the repository by cloning the release tag v9.0.109 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.101

You can build .NET 9.0 from the repository by cloning the release tag v9.0.101 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.7

You can build .NET 9.0 from the repository by cloning the release tag v9.0.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.6

You can build .NET 9.0 from the repository by cloning the release tag v9.0.6 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.5

You can build .NET 9.0 from the repository by cloning the release tag v9.0.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.4

You can build .NET 9.0 from the repository by cloning the release tag v9.0.4 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.3

You can build .NET 9.0 from the repository by cloning the release tag v9.0.3 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.2

You can build .NET 9.0 from the repository by cloning the release tag v9.0.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.1

You can build .NET 9.0 from the repository by cloning the release tag v9.0.1 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

Commits viewable in compare view.

Updated Microsoft.Extensions.Options from 10.0.0 to 10.0.3.

Release notes

Sourced from Microsoft.Extensions.Options's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.ServiceDiscovery from 10.0.0 to 10.3.0.

Release notes

Sourced from Microsoft.Extensions.ServiceDiscovery's releases.

10.3.0

What's Changed

New Contributors

... (truncated)

10.2.0

What's Changed

New Contributors

Full Changelog: dotnet/extensions@v10.1...v10.2.0

10.1.0

What's Changed

Commits viewable in compare view.

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
Bump the microsoftextensions group with 6 updates
7123ed6 
Bumps Microsoft.Extensions.ApiDescription.Server from 10.0.0 to 10.0.3
Bumps Microsoft.Extensions.Http from 9.0.0 to 10.0.3
Bumps Microsoft.Extensions.Http.Resilience from 10.0.0 to 10.3.0
Bumps Microsoft.Extensions.Logging.Debug from 9.0.0 to 10.0.3
Bumps Microsoft.Extensions.Options from 10.0.0 to 10.0.3
Bumps Microsoft.Extensions.ServiceDiscovery from 10.0.0 to 10.3.0

---
updated-dependencies:
- dependency-name: Microsoft.Extensions.ApiDescription.Server
  dependency-version: 10.0.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: microsoftextensions
- dependency-name: Microsoft.Extensions.Http
  dependency-version: 10.0.3
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: microsoftextensions
- dependency-name: Microsoft.Extensions.Http.Resilience
  dependency-version: 10.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: microsoftextensions
- dependency-name: Microsoft.Extensions.Logging.Debug
  dependency-version: 10.0.3
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: microsoftextensions
- dependency-name: Microsoft.Extensions.Logging.Debug
  dependency-version: 10.0.3
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: microsoftextensions
- dependency-name: Microsoft.Extensions.Options
  dependency-version: 10.0.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: microsoftextensions
- dependency-name: Microsoft.Extensions.ServiceDiscovery
  dependency-version: 10.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: microsoftextensions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Feb 16, 2026
@socket-security
Copy link

socket-security bot commented Feb 16, 2026

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

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Addednuget/​microsoft.extensions.telemetry@​10.3.010010090100100
Addednuget/​microsoft.extensions.http.resilience@​10.3.010010090100100
Addednuget/​microsoft.extensions.resilience@​10.3.010010090100100
Addednuget/​microsoft.extensions.dependencyinjection.autoactivation@​10.3.010010090100100
Addednuget/​microsoft.extensions.ambientmetadata.application@​10.3.010010090100100
Addednuget/​microsoft.extensions.servicediscovery.abstractions@​10.3.010010090100100
Addednuget/​microsoft.extensions.servicediscovery@​10.3.010010090100100
Addednuget/​microsoft.extensions.diagnostics.exceptionsummarization@​10.3.010010090100100
Addednuget/​microsoft.extensions.compliance.abstractions@​10.3.010010090100100
Addednuget/​microsoft.extensions.http.diagnostics@​10.3.010010090100100
Addednuget/​microsoft.extensions.telemetry.abstractions@​10.3.010010090100100
Updatednuget/​microsoft.extensions.logging.debug@​9.0.0 ⏵ 10.0.31001009010070
Updatednuget/​microsoft.extensions.primitives@​9.0.11 ⏵ 10.0.3100 +11009010070
Updatednuget/​microsoft.extensions.logging.configuration@​9.0.11 ⏵ 10.0.3100 +21009010070 -30
Updatednuget/​microsoft.extensions.objectpool@​9.0.11 ⏵ 10.0.3100 +310090100100
Updatednuget/​microsoft.extensions.dependencyinjection.abstractions@​9.0.11 ⏵ 10.0.3100 +21009010070
Updatednuget/​microsoft.extensions.configuration.binder@​9.0.11 ⏵ 10.0.3100 +81009010070 -30
Updatednuget/​microsoft.extensions.configuration.abstractions@​9.0.11 ⏵ 10.0.3100 +21009010070 -30
Updatednuget/​microsoft.extensions.configuration@​9.0.11 ⏵ 10.0.3100 +41009010070 -30
Updatednuget/​microsoft.extensions.http@​9.0.0 ⏵ 10.0.31001009010070
Updatednuget/​microsoft.extensions.options.configurationextensions@​9.0.11 ⏵ 10.0.3100 +21009010070 -30
Updatednuget/​microsoft.extensions.diagnostics.abstractions@​9.0.11 ⏵ 10.0.3100 +41009010070 -30
Updatednuget/​microsoft.extensions.logging.abstractions@​9.0.11 ⏵ 10.0.3100 +411009010070
Updatednuget/​microsoft.extensions.diagnostics@​9.0.11 ⏵ 10.0.3100 +41009010070 -30
Updatednuget/​microsoft.extensions.fileproviders.abstractions@​9.0.11 ⏵ 10.0.3100 +21009010070
Updatednuget/​microsoft.extensions.hosting.abstractions@​9.0.11 ⏵ 10.0.3100 +51009010070 -30
Updatednuget/​microsoft.extensions.options@​9.0.11 ⏵ 10.0.3100 +51009010070
Updatednuget/​microsoft.extensions.logging@​9.0.11 ⏵ 10.0.3100 +21009010070
Updatednuget/​microsoft.extensions.dependencyinjection@​9.0.11 ⏵ 10.0.3100 +31009010070
Updatednuget/​microsoft.extensions.servicediscovery.yarp@​10.0.0 ⏵ 10.3.0100 +210090100100
Updatednuget/​microsoft.extensions.apidescription.server@​10.0.0 ⏵ 10.0.398 +36100100100100

View full report

@socket-security
Copy link

socket-security bot commented Feb 16, 2026

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 High
License policy violation: nuget microsoft.extensions.configuration.abstractions

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

License: NIST-Software - the applicable license policy does not allow this license (4) (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.configuration.abstractions@10.0.3

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.configuration.abstractions@10.0.3. 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.

Warn High
License policy violation: nuget microsoft.extensions.configuration.abstractions

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.telemetry@10.3.0 → nuget/microsoft.extensions.resilience@10.3.0 → nuget/microsoft.extensions.dependencyinjection.autoactivation@10.3.0 → nuget/microsoft.extensions.ambientmetadata.application@10.3.0 → nuget/microsoft.extensions.servicediscovery.abstractions@10.3.0 → nuget/microsoft.extensions.servicediscovery@10.3.0 → nuget/microsoft.extensions.http.diagnostics@10.3.0 → nuget/microsoft.extensions.configuration@9.0.0 → nuget/microsoft.extensions.logging.configuration@9.0.0 → nuget/asp.versioning.http.client@8.1.0 → nuget/grpc.net.clientfactory@2.71.0 → nuget/opentelemetry@1.12.0 → nuget/opentelemetry.extensions.hosting@1.12.0 → nuget/opentelemetry.instrumentation.http@1.12.0 → nuget/communitytoolkit.aspire.ollamasharp@9.8.0-beta.395 → nuget/microsoft.extensions.servicediscovery.abstractions@10.0.0 → nuget/microsoft.extensions.servicediscovery@10.0.0 → nuget/aspire.rabbitmq.client@13.0.1 → nuget/aspire.stackexchange.redis@13.0.1 → nuget/aspire.npgsql.entityframeworkcore.postgresql@13.0.1 → nuget/microsoft.extensions.configuration.abstractions@9.0.13

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.configuration.abstractions@9.0.13. 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.

Warn High
License policy violation: nuget microsoft.extensions.configuration.binder

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

License: NIST-Software - the applicable license policy does not allow this license (4) (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.configuration.binder@10.0.3

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.configuration.binder@10.0.3. 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.

Warn High
License policy violation: nuget microsoft.extensions.configuration.binder

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.telemetry@10.3.0 → nuget/microsoft.extensions.resilience@10.3.0 → nuget/microsoft.extensions.ambientmetadata.application@10.3.0 → nuget/microsoft.extensions.servicediscovery.abstractions@10.3.0 → nuget/microsoft.extensions.servicediscovery@10.3.0 → nuget/microsoft.extensions.http.diagnostics@10.3.0 → nuget/microsoft.extensions.logging.configuration@9.0.0 → nuget/asp.versioning.http.client@8.1.0 → nuget/grpc.net.clientfactory@2.71.0 → nuget/opentelemetry@1.12.0 → nuget/communitytoolkit.aspire.ollamasharp@9.8.0-beta.395 → nuget/microsoft.extensions.servicediscovery.abstractions@10.0.0 → nuget/microsoft.extensions.servicediscovery@10.0.0 → nuget/aspire.rabbitmq.client@13.0.1 → nuget/aspire.stackexchange.redis@13.0.1 → nuget/aspire.npgsql.entityframeworkcore.postgresql@13.0.1 → nuget/microsoft.extensions.configuration.binder@9.0.13

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.configuration.binder@9.0.13. 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.

Warn High
License policy violation: nuget microsoft.extensions.configuration

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

License: NIST-Software - the applicable license policy does not allow this license (4) (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.configuration@10.0.3

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.configuration@10.0.3. 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.

Warn High
License policy violation: nuget microsoft.extensions.configuration

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.telemetry@10.3.0 → nuget/microsoft.extensions.resilience@10.3.0 → nuget/microsoft.extensions.ambientmetadata.application@10.3.0 → nuget/microsoft.extensions.servicediscovery@10.3.0 → nuget/microsoft.extensions.http.diagnostics@10.3.0 → nuget/microsoft.extensions.logging.configuration@9.0.0 → nuget/asp.versioning.http.client@8.1.0 → nuget/grpc.net.clientfactory@2.71.0 → nuget/opentelemetry@1.12.0 → nuget/opentelemetry.instrumentation.http@1.12.0 → nuget/communitytoolkit.aspire.ollamasharp@9.8.0-beta.395 → nuget/microsoft.extensions.servicediscovery@10.0.0 → nuget/microsoft.extensions.configuration@9.0.13

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.configuration@9.0.13. 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.

Warn High
License policy violation: nuget microsoft.extensions.dependencyinjection.abstractions

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

License: NIST-Software - the applicable license policy does not allow this license (4) (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.dependencyinjection.abstractions@10.0.3

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.dependencyinjection.abstractions@10.0.3. 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.

Warn High
License policy violation: nuget microsoft.extensions.dependencyinjection.abstractions

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.telemetry@10.3.0 → nuget/microsoft.extensions.resilience@10.3.0 → nuget/microsoft.extensions.dependencyinjection.autoactivation@10.3.0 → nuget/microsoft.extensions.ambientmetadata.application@10.3.0 → nuget/microsoft.extensions.servicediscovery.abstractions@10.3.0 → nuget/microsoft.extensions.servicediscovery@10.3.0 → nuget/microsoft.extensions.diagnostics.exceptionsummarization@10.3.0 → nuget/microsoft.extensions.compliance.abstractions@10.3.0 → nuget/microsoft.extensions.http.diagnostics@10.3.0 → nuget/microsoft.extensions.telemetry.abstractions@10.3.0 → nuget/microsoft.extensions.dependencyinjection@9.0.0 → nuget/microsoft.extensions.logging.configuration@9.0.0 → nuget/polly.extensions@8.4.2 → nuget/asp.versioning.http.client@8.1.0 → nuget/grpc.net.client@2.71.0 → nuget/grpc.net.clientfactory@2.71.0 → nuget/opentelemetry@1.12.0 → nuget/opentelemetry.api.providerbuilderextensions@1.12.0 → nuget/opentelemetry.extensions.hosting@1.12.0 → nuget/opentelemetry.instrumentation.http@1.12.0 → nuget/fluentvalidation.dependencyinjectionextensions@12.0.0 → nuget/microsoft.codeanalysis.workspaces.msbuild@4.14.0 → nuget/mediatr@13.0.0 → nuget/communitytoolkit.aspire.ollamasharp@9.8.0-beta.395 → nuget/stackexchange.redis@2.9.32 → nuget/microsoft.extensions.servicediscovery.abstractions@10.0.0 → nuget/microsoft.extensions.servicediscovery@10.0.0 → nuget/npgsql@10.0.0 → nuget/npgsql.dependencyinjection@10.0.0 → nuget/aspire.rabbitmq.client@13.0.1 → nuget/aspire.stackexchange.redis@13.0.1 → nuget/aspire.npgsql.entityframeworkcore.postgresql@13.0.1 → nuget/microsoft.extensions.dependencyinjection.abstractions@9.0.13

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.dependencyinjection.abstractions@9.0.13. 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.

Warn High
License policy violation: nuget microsoft.extensions.dependencyinjection

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

License: NIST-Software - the applicable license policy does not allow this license (4) (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.dependencyinjection@10.0.3

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.dependencyinjection@10.0.3. 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.

Warn High
License policy violation: nuget microsoft.extensions.dependencyinjection

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.telemetry@10.3.0 → nuget/microsoft.extensions.servicediscovery@10.3.0 → nuget/microsoft.extensions.http.diagnostics@10.3.0 → nuget/microsoft.extensions.logging@8.0.0 → nuget/microsoft.extensions.logging@9.0.0 → nuget/microsoft.extensions.logging.configuration@9.0.0 → nuget/asp.versioning.http.client@8.1.0 → nuget/grpc.net.clientfactory@2.71.0 → nuget/opentelemetry@1.12.0 → nuget/microsoft.codeanalysis.workspaces.msbuild@4.14.0 → nuget/mediatr@13.0.0 → nuget/microsoft.extensions.azure@1.13.0 → nuget/communitytoolkit.aspire.ollamasharp@9.8.0-beta.395 → nuget/microsoft.extensions.servicediscovery@10.0.0 → nuget/microsoft.extensions.dependencyinjection@9.0.13

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.dependencyinjection@9.0.13. 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.

Warn High
License policy violation: nuget microsoft.extensions.diagnostics.abstractions

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

License: NIST-Software - the applicable license policy does not allow this license (4) (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.diagnostics.abstractions@10.0.3

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.diagnostics.abstractions@10.0.3. 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.

Warn High
License policy violation: nuget microsoft.extensions.diagnostics.abstractions

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.resilience@10.3.0 → nuget/microsoft.extensions.dependencyinjection.autoactivation@10.3.0 → nuget/microsoft.extensions.ambientmetadata.application@10.3.0 → nuget/microsoft.extensions.servicediscovery@10.3.0 → nuget/microsoft.extensions.http.diagnostics@10.3.0 → nuget/asp.versioning.http.client@8.1.0 → nuget/grpc.net.clientfactory@2.71.0 → nuget/opentelemetry@1.12.0 → nuget/opentelemetry.extensions.hosting@1.12.0 → nuget/communitytoolkit.aspire.ollamasharp@9.8.0-beta.395 → nuget/microsoft.extensions.servicediscovery@10.0.0 → nuget/aspire.rabbitmq.client@13.0.1 → nuget/aspire.stackexchange.redis@13.0.1 → nuget/aspire.npgsql.entityframeworkcore.postgresql@13.0.1 → nuget/microsoft.extensions.diagnostics.abstractions@9.0.13

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.diagnostics.abstractions@9.0.13. 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.

Warn High
License policy violation: nuget microsoft.extensions.diagnostics

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

License: NIST-Software - the applicable license policy does not allow this license (4) (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.diagnostics@10.0.3

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.diagnostics@10.0.3. 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.

Warn High
License policy violation: nuget microsoft.extensions.diagnostics

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.resilience@10.3.0 → nuget/microsoft.extensions.servicediscovery@10.3.0 → nuget/microsoft.extensions.http.diagnostics@10.3.0 → nuget/asp.versioning.http.client@8.1.0 → nuget/grpc.net.clientfactory@2.71.0 → nuget/communitytoolkit.aspire.ollamasharp@9.8.0-beta.395 → nuget/microsoft.extensions.servicediscovery@10.0.0 → nuget/microsoft.extensions.diagnostics@9.0.13

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.diagnostics@9.0.13. 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.

Warn High
License policy violation: nuget microsoft.extensions.fileproviders.abstractions

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

License: NIST-Software - the applicable license policy does not allow this license (4) (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.fileproviders.abstractions@10.0.3

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.fileproviders.abstractions@10.0.3. 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.

Warn High
License policy violation: nuget microsoft.extensions.fileproviders.abstractions

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.dependencyinjection.autoactivation@10.3.0 → nuget/microsoft.extensions.ambientmetadata.application@10.3.0 → nuget/opentelemetry.extensions.hosting@1.12.0 → nuget/aspire.rabbitmq.client@13.0.1 → nuget/aspire.stackexchange.redis@13.0.1 → nuget/aspire.npgsql.entityframeworkcore.postgresql@13.0.1 → nuget/microsoft.extensions.fileproviders.abstractions@9.0.13

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.fileproviders.abstractions@9.0.13. 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.

Warn High
License policy violation: nuget microsoft.extensions.hosting.abstractions

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

License: NIST-Software - the applicable license policy does not allow this license (4) (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.hosting.abstractions@10.0.3

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.hosting.abstractions@10.0.3. 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.

Warn High
License policy violation: nuget microsoft.extensions.hosting.abstractions

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.dependencyinjection.autoactivation@10.3.0 → nuget/microsoft.extensions.ambientmetadata.application@10.3.0 → nuget/opentelemetry.extensions.hosting@1.12.0 → nuget/aspire.rabbitmq.client@13.0.1 → nuget/aspire.stackexchange.redis@13.0.1 → nuget/aspire.npgsql.entityframeworkcore.postgresql@13.0.1 → nuget/microsoft.extensions.hosting.abstractions@9.0.13

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.hosting.abstractions@9.0.13. 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.

Warn High
License policy violation: nuget microsoft.extensions.http

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

License: NIST-Software - the applicable license policy does not allow this license (4) (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.http@10.0.3

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.http@10.0.3. 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.

Warn High
License policy violation: nuget microsoft.extensions.http

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.servicediscovery@10.3.0 → nuget/microsoft.extensions.http.diagnostics@10.3.0 → nuget/asp.versioning.http.client@8.1.0 → nuget/grpc.net.clientfactory@2.71.0 → nuget/communitytoolkit.aspire.ollamasharp@9.8.0-beta.395 → nuget/microsoft.extensions.servicediscovery@10.0.0 → nuget/microsoft.extensions.http@9.0.13

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.http@9.0.13. 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.

Warn High
License policy violation: nuget microsoft.extensions.logging.abstractions

License: GPL-2.0-or-later WITH Classpath-exception-2.0 - the applicable license policy does not allow this license (4). the applicable license policy does not allow this license exception (THIRD-PARTY-NOTICES.TXT)

License: NIST-Software - the applicable license policy does not allow this license (4) (THIRD-PARTY-NOTICES.TXT)

From: src/Basket.API/packages.lock.json → nuget/microsoft.extensions.logging.abstractions@10.0.3

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/microsoft.extensions.logging.abstractions@10.0.3. 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.

See 13 more rows in the dashboard

View full report

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

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants