Skip to content

Bump the crispywaffle group with 2 updates - #597

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/Src/Sankhya/crispywaffle-85587f2628
Open

Bump the crispywaffle group with 2 updates#597
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/Src/Sankhya/crispywaffle-85587f2628

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 27, 2026

Copy link
Copy Markdown
Contributor

Updated CrispyWaffle from 10.0.1513 to 10.2.17.

Release notes

Sourced from CrispyWaffle's releases.

10.2.17

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.16...v10.2.17

10.2.16

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.15...v10.2.16

10.2.15

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.14...v10.2.15

10.2.14

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.13...v10.2.14

10.2.13

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.12...v10.2.13

10.2.12

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.11...v10.2.12

10.2.11

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.10...v10.2.11

10.2.10

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.9...v10.2.10

10.2.9

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.8...v10.2.9

10.2.8

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.7...v10.2.8

10.2.7

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.6...v10.2.7

10.2.6

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.5...v10.2.6

10.2.5

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.4...v10.2.5

10.2.4

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.3...v10.2.4

10.2.3

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.2...v10.2.3

10.2.2

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.1...v10.2.2

10.2.1

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.0...v10.2.1

10.2.0

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.1.0...v10.2.0

10.1.0

What's Changed

New Contributors

Full Changelog: guibranco/CrispyWaffle@v10.0.1513...v10.1.0

Commits viewable in compare view.

Updated CrispyWaffle.Configuration from 10.0.1513 to 10.2.17.

Release notes

Sourced from CrispyWaffle.Configuration's releases.

10.2.17

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.16...v10.2.17

10.2.16

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.15...v10.2.16

10.2.15

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.14...v10.2.15

10.2.14

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.13...v10.2.14

10.2.13

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.12...v10.2.13

10.2.12

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.11...v10.2.12

10.2.11

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.10...v10.2.11

10.2.10

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.9...v10.2.10

10.2.9

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.8...v10.2.9

10.2.8

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.7...v10.2.8

10.2.7

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.6...v10.2.7

10.2.6

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.5...v10.2.6

10.2.5

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.4...v10.2.5

10.2.4

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.3...v10.2.4

10.2.3

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.2...v10.2.3

10.2.2

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.1...v10.2.2

10.2.1

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.2.0...v10.2.1

10.2.0

What's Changed

Full Changelog: guibranco/CrispyWaffle@v10.1.0...v10.2.0

10.1.0

What's Changed

New Contributors

Full Changelog: guibranco/CrispyWaffle@v10.0.1513...v10.1.0

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 crispywaffle group with 2 updates
1b36b66 
Bumps CrispyWaffle from 10.0.1513 to 10.2.17
Bumps CrispyWaffle.Configuration from 10.0.1513 to 10.2.17

---
updated-dependencies:
- dependency-name: CrispyWaffle
  dependency-version: 10.2.17
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: crispywaffle
- dependency-name: CrispyWaffle.Configuration
  dependency-version: 10.2.17
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: crispywaffle
...

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 nuget Package updates (NuGet) packages Package updates labels Jul 27, 2026
@github-actions github-actions Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jul 27, 2026
@socket-security

socket-security Bot commented Jul 27, 2026

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
Updatednuget/​crispywaffle.configuration@​10.0.1513 ⏵ 10.2.179910090100100
Updatednuget/​crispywaffle@​10.0.1513 ⏵ 10.2.1794 +110090100100

View full report

@socket-security

socket-security Bot commented Jul 27, 2026

Copy link
Copy Markdown

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Block Medium
Network access: nuget system.security.permissions

Location: Package overview

From: Src/Sankhya/Sankhya.csproj → nuget/crispywaffle@10.2.17 → nuget/system.security.permissions@10.0.10

ℹ Read more on: This package | This alert | What is network access?

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: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/system.security.permissions@10.0.10. 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.

Block Medium
System shell access: nuget system.security.permissions

Location: Package overview

From: Src/Sankhya/Sankhya.csproj → nuget/crispywaffle@10.2.17 → nuget/system.security.permissions@10.0.10

ℹ Read more on: This package | This alert | What is shell access?

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: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/system.security.permissions@10.0.10. 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.

Block Medium
Dynamic code execution: nuget system.security.permissions

Location: Package overview

From: Src/Sankhya/Sankhya.csproj → nuget/crispywaffle@10.2.17 → nuget/system.security.permissions@10.0.10

ℹ Read more on: This package | This alert | What is dynamic code execution?

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: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore nuget/system.security.permissions@10.0.10. 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.

Block Medium
Network access: nuget system.windows.extensions

Location: Package overview

From: Src/Sankhya/Sankhya.csproj → nuget/crispywaffle@10.2.17 → nuget/system.windows.extensions@10.0.10

ℹ Read more on: This package | This alert | What is network access?

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: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

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

Block Medium
System shell access: nuget system.windows.extensions

Location: Package overview

From: Src/Sankhya/Sankhya.csproj → nuget/crispywaffle@10.2.17 → nuget/system.windows.extensions@10.0.10

ℹ Read more on: This package | This alert | What is shell access?

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: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

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

Block Medium
Dynamic code execution: nuget system.windows.extensions

Location: Package overview

From: Src/Sankhya/Sankhya.csproj → nuget/crispywaffle@10.2.17 → nuget/system.windows.extensions@10.0.10

ℹ Read more on: This package | This alert | What is dynamic code execution?

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: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code.

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

Block Low
Potential code anomaly (AI signal): nuget crispywaffle is 68.0% likely to have a medium risk anomaly

Notes: No direct evidence of explicit malware (e.g., backdoor, credential theft, reverse shell) is present in this fragment. However, there are notable high-impact security risks: (1) caller-controlled XSLT execution via XmlTemplateRender without visible security hardening, and (2) runtime assembly loading of missing referenced assemblies in ServiceLocator, which increases supply-chain/assembly-hijack risk in compromised environments. Additionally, the library performs an outbound HTTP call to api.ipify.org during static initialization and provides filesystem write/delete primitives when given paths.

Confidence: 0.68

Severity: 0.62

From: Src/Sankhya/Sankhya.csproj → nuget/crispywaffle@10.2.17

ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly?

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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

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

Block Low
Filesystem access: nuget system.windows.extensions

Location: Package overview

From: Src/Sankhya/Sankhya.csproj → nuget/crispywaffle@10.2.17 → nuget/system.windows.extensions@10.0.10

ℹ Read more on: This package | This alert | What is filesystem access?

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: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

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

@AppVeyorBot

AppVeyorBot commented Jul 27, 2026

Copy link
Copy Markdown

❌ Build Sankhya-SDK-dotnet 5.0.990 failed (commit b9dc6c2820 by @dependabot[bot])

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

Reviewers

No reviews

Assignees

@guibranco guibranco

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .net code nuget Package updates (NuGet) packages Package updates size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@AppVeyorBot @guibranco