fsharp-security-review

To audit F# code for security vulnerabilities, you can use this skill to analyze input validation, serialization safety, secrets handling, and dependency risks. It systematically identifies potential flaws by checking unsafe interop and boundary data flow.

Common F# security pitfalls involve unsafe interop and boundary data flow where the type system's immutability may create false positives. This audit focuses on critical boundary checks rather than assuming type safety eliminates all input validation or serialization vulnerabilities.

Performing a pre-deployment security review of an F# microservice involves analyzing the codebase for input validation flaws, secrets management issues, and dependency risks. This skill systematically checks the directory's code to ensure resilience against common web exploits.

Yes, this F# security audit checks for serialization vulnerabilities along with input validation flaws, secrets handling issues, and dependency risks. It analyzes code to ensure data boundary checks are robust against common attack vectors.

The audit handles false positives in F# code by applying tailored rules that account for F#'s type system and immutability. It filters results based on shared security review guidelines, focusing on genuine boundary data flow and unsafe interop issues.

The best way to find secrets handling issues in F# applications is to run an in-depth security audit on the current directory. This skill systematically analyzes the code to identify hardcoded secrets and mitigate potential exposure risks.