.NET async cancellation and fire-and-forget lifecycle
.NET async cancellation and fire-and-forget lifecycle: Propagate CancellationToken and observe every Task failure.
- code hygiene
- audit
- remediation
Browse reviewed workflows for common security tasks. Search by intent, filter by outcome and review quality, share a filtered URL, or retrieve the same bounded context through JSON and MCP.
Choose the smallest recipe that matches the outcome you need. Every workflow is structured for people to inspect and agents to retrieve, with explicit inputs, guardrails, evidence, and stop conditions.
Showing 18 of 155 curated recipes.
Dense list view.NET async cancellation and fire-and-forget lifecycle: Propagate CancellationToken and observe every Task failure.
.NET disposable and async-disposable lifecycle: Dispose synchronous and asynchronous resources exactly once after their final use.
.NET LINQ enumeration and EF query boundaries: Avoid repeated enumeration, client evaluation, N+1 loading, and leaked query lifetimes.
.NET nullable and analyzer suppression debt: Resolve nullable and analyzer warnings without null-forgiving or pragma expansion.
C and C++ atomic, lock, and thread lifecycle: Remove data races, lock-order hazards, and detached thread lifetimes.
C and C++ bounds, integer, and undefined-behavior hygiene: Remove unchecked bounds, lossy arithmetic, lifetime, and undefined-behavior hazards.
C and C++ compiler warning and suppression debt: Resolve portable compiler diagnostics without blanket flags or pragmas.
C and C++ const, span, view, and lifetime hygiene: Make mutation and non-owning view lifetimes explicit.
C and C++ ownership, RAII, and resource lifecycle: Make memory, file, socket, lock, and handle ownership explicit.
CI workflow timeout, concurrency, and cache hygiene: Bound CI jobs and prevent stale caches and duplicate workflow races.
Assess CIS Controls v8.1 evidence readiness: verify applicability, map official requirements to artifacts, record gaps, and plan remediation.
Assess CISA Cross-Sector CPGs evidence readiness: verify applicability, map official requirements to artifacts, record gaps, and plan remediation.
Assess CJIS Security Policy v6.1 evidence readiness: verify applicability, map official requirements to artifacts, record gaps, and plan remediation.
Assess CMMC 2.0 evidence readiness: verify applicability, map official requirements to artifacts, record gaps, and plan remediation.
Assess COBIT 2019 evidence readiness: verify applicability, map official requirements to artifacts, record gaps, and plan remediation.
Complexity and long-function reduction: Reduce hard-to-review control flow without changing behavior. Includes scoped detection, verification, and stop conditions.
Configuration validation and default hygiene: Make invalid configuration fail clearly and defaults behave consistently.
Container signal, healthcheck, and shutdown hygiene: Make PID 1 signal handling, readiness, health, and graceful shutdown correct.
Clear one or more filters, or use the dedicated database for vulnerability intelligence.
Open CVE DatabaseRecipes guide people and agents; they do not enforce policy.
Back recipes with scoped credentials, branch protections, CODEOWNERS, and required CI. Never treat generated remediation as proof that a system is safe.
Use the curated JSON feed for workflow discovery. For exact or filtered vulnerability intelligence, use the separate CVE Database and its dedicated MCP tools. MCP access should remain read-only unless the task explicitly authorizes a specific write.
Use approved MCP servers as read-only evidence.
Do not create tickets, push branches, rotate secrets, deploy changes, or alter
cloud resources through MCP unless this task explicitly grants that permission.
Maintainers can run recipes_quality_report through MCP to find recipes that
need stronger inputs, when-to-use guidance, output contracts, verification, or
guardrails. Those same headings also drive search quality on this site.
Contributions can add workflows, evidence checks, toolsets, templates, or reviewed CVE overrides. Remove secrets, internal hostnames, customer data, and private vulnerability details first, then follow the contribution process.