Bump the crispywaffle group with 1 update

[dependabot]

Updated CrispyWaffle from 10.2.6 to 10.2.12.

Release notes

Sourced from CrispyWaffle's releases.

10.2.12

What's Changed

• Bump the dependencies group with 8 updates by @​dependabot[bot] in Bump the dependencies group with 8 updates guibranco/CrispyWaffle#968

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

10.2.11

What's Changed

• Bump the testing group with 1 update by @​dependabot[bot] in Bump the testing group with 1 update guibranco/CrispyWaffle#966

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

10.2.10

What's Changed

• Bump the microsoft group with 2 updates by @​dependabot[bot] in Bump the microsoft group with 2 updates guibranco/CrispyWaffle#964

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

10.2.9

What's Changed

• Bump the dependencies group with 10 updates by @​dependabot[bot] in Bump the dependencies group with 10 updates guibranco/CrispyWaffle#962

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

10.2.8

What's Changed

• Bump the microsoft group with 1 update by @​dependabot[bot] in Bump the microsoft group with 1 update guibranco/CrispyWaffle#961

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

10.2.7

What's Changed

• chore(deps): bump the github-actions group with 7 updates by @​dependabot[bot] in chore(deps): bump the github-actions group with 7 updates guibranco/CrispyWaffle#960

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

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

[guibranco]

Automatically approved by gstraccini[bot]

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	system.text.json@​10.0.10
	system.io.pipelines@​10.0.10
	system.security.permissions@​10.0.10
	system.text.encodings.web@​10.0.10
	microsoft.bcl.asyncinterfaces@​10.0.5 ⏵ 10.0.10
	crispywaffle@​10.2.12

View full report

[socket-security]

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		Network access: nuget system.security.permissions Location: Package overview From: Src/EditoraInovacao.Sankhya.Entities/packages.lock.json → 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		System shell access: nuget system.security.permissions Location: Package overview From: Src/EditoraInovacao.Sankhya.Entities/packages.lock.json → 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		Dynamic code execution: nuget system.security.permissions Location: Package overview From: Src/EditoraInovacao.Sankhya.Entities/packages.lock.json → 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		Network access: nuget system.windows.extensions Location: Package overview From: Src/EditoraInovacao.Sankhya.Entities/packages.lock.json → nuget/system.security.permissions@10.0.10 → 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		System shell access: nuget system.windows.extensions Location: Package overview From: Src/EditoraInovacao.Sankhya.Entities/packages.lock.json → nuget/system.security.permissions@10.0.10 → 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		Dynamic code execution: nuget system.windows.extensions Location: Package overview From: Src/EditoraInovacao.Sankhya.Entities/packages.lock.json → nuget/system.security.permissions@10.0.10 → 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		Potential code anomaly (AI signal): nuget crispywaffle is 65.0% likely to have a medium risk anomaly Notes: Overall risk is driven by XmlTemplateRender: it loads and transforms XSLT directly from the provided template string with XslCompiledTransform.Load/Transform, which is a high-risk sink if templates are user-influenced (XSLT injection / unsafe transformation execution). Additionally, the library performs an outbound network request to https://api.ipify.org to obtain external IP, which is a privacy/egress concern. Other components (DynamicSerialization, filesystem save/logging, and assembly auto-loading) add general security considerations but are not definitive malware indicators from this snippet alone. Confidence: 0.65 Severity: 0.68 From: Src/EditoraInovacao.Sankhya.Entities/packages.lock.json → nuget/crispywaffle@10.2.12 ℹ 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.12. 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		Filesystem access: nuget system.windows.extensions Location: Package overview From: Src/EditoraInovacao.Sankhya.Entities/packages.lock.json → nuget/system.security.permissions@10.0.10 → 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

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

2026-07-20T07:30:56Z INF scanning for exposed secrets...
7:30AM INF 372 commits scanned.
2026-07-20T07:30:56Z INF scan completed in 286ms
2026-07-20T07:30:56Z INF no leaks found

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud