Skip to content
Back to search

FSharp.Analyzers.SDK

Library for building custom analyzers for F# / FSAC

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/ionide/FSharp.Analyzers.SDK with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/ionide/FSharp.Analyzers.SDK'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/ionide--fsharp-analyzers-sdk/badge.svg)](/listings/ionide--fsharp-analyzers-sdk)

HTML

<a href="/listings/ionide--fsharp-analyzers-sdk"><img src="/api/listings/ionide--fsharp-analyzers-sdk/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 63 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Ionide FSharp.Analyzers.SDK
  2. Library used for building custom analyzers for FSAC / F# editors.
  3. F# analyzers are live, real-time, project based plugins that enables to diagnose source code and surface custom errors, warnings and code fixes into editor. Read more about analyzers here - https://medium.com/lambda-factory/introducing-f-analyzers-772487889429
  4. ## How to build
  5. 1. Install the .NET SDK version specified in `global.json`
  6. 2. `dotnet tool restore`
  7. 3. Open and build in your favorite IDE, or use `dotnet build`
  8. ## How to run sample
  9. 1. `dotnet build -c Release`
  10. 2. Run the console application:
  11. ```shell
  12. dotnet run --project src\FSharp.Analyzers.Cli\FSharp.Analyzers.Cli.fsproj -- --project ./samples/OptionAnalyzer/OptionAnalyzer.fsproj --analyzers-path ./artifacts/bin/OptionAnalyzer/release --verbosity d
  13. ```
  14. You can also set up a run configuration of FSharp.Analyzers.Cli in your favorite IDE using similar arguments. This also allows you to debug FSharp.Analyzers.Cli.
  15. ## Using Analyzers
  16. Checkout our [Getting Started](https://ionide.io/FSharp.Analyzers.SDK/content/getting-started/Installing%20Analyzers.html) guide for analyzer users!
  17. ### Upgrading with an AI agent
  18. This repository ships an [agent skill](./skills/upgrade-fsharp-analyzers/SKILL.md) that upgrades the `fsharp-analyzers` tool and your analyzer packages to a matching set of versions, re-runs the analyzers and reports what is new. Install it globally with:
  19. ```shell
  20. npx skills add ionide/FSharp.Analyzers.SDK --skill upgrade-fsharp-analyzers -g
  21. ```
  22. Then ask your agent to "upgrade the F# analyzers" in a repository that uses them.
  23. ## Writing Analyzers
  24. Checkout our [Getting Started](https://ionide.io/FSharp.Analyzers.SDK/content/Getting%20Started%20Writing.html) guide for analyzer authors!
  25. ## How to contribute
  26. *Imposter syndrome disclaimer*: I want your help. No really, I do.
  27. There might be a little voice inside that tells you you're not ready; that you need to do one more tutorial, or learn another framework, or write a few more blog posts before you can help me with this project.
  28. I assure you, that's not the case.
  29. This project has some clear Contribution Guidelines and expectations that you can [read here](https://github.com/Krzysztof-Cieslak/FSharp.Analyzers.SDK/blob/main/CONTRIBUTING.md).
  30. The contribution guidelines outline the process that you'll need to follow to get a patch merged. By making expectations and process explicit, I hope it will make it easier for you to contribute.
  31. And you don't just have to write code. You can help out by writing documentation, tests, or even by giving feedback about this work. (And yes, that includes giving feedback about the contribution guidelines.)
  32. Thank you for contributing!
  33. ## Contributing and copyright
  34. The project is hosted on [GitHub](https://github.com/Krzysztof-Cieslak/FSharp.Analyzers.SDK) where you can [report issues](https://github.com/Krzysztof-Cieslak/FSharp.Analyzers.SDK/issues), fork
  35. the project and submit pull requests.
  36. The library is available under [MIT license](https://github.com/Krzysztof-Cieslak/FSharp.Analyzers.SDK/blob/main/LICENSE.md), which allows modification and redistribution for both commercial and non-commercial purposes.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.