I build developer tooling for PowerShell -- static analysis that runs where the code is being written, rather than as a separate lint step afterwards.

Real-time PowerShell diagnostics and PSScriptAnalyzer fixes inside Claude Code, as it edits your .ps1 / .psm1 / .psd1. Built on PowerShell Editor Services.

/plugin marketplace add manderse21/claude-powershell-lsp
/plugin install powershell-lsp

28 releases. GPL-3.0. Published releases begin at v1.17.0; the 15 tags before it are lightweight pre-publication markers with no release attached. Every published release from v1.17.0 on carries a CycloneDX SBOM and a Sigstore keyless build provenance attestation, with one deliberate exception -- v1.18.1 was published retroactively and does not reproduce build assets that did not exist at its original build time. TRUST.md states plainly what those attestations do not prove.

• PowerShell static analysis -- PSScriptAnalyzer rule curation, false-positive rate measured against a fixed corpus, SARIF output
• Language Server Protocol integration, and how agent hosts drive a language server in practice
• Windows-first tooling -- PowerShell 5.1 and 7.x semantics, encoding and codepage behaviour, process lifecycle hygiene

• Upstream first. Bugs get filed and fixed at the source when that is where they belong -- PowerShell Editor Services #2297 and #2300, and a handful in Claude Code.
• Releases are reproducible and signed; third-party actions are pinned to commit SHAs; CI gates every merge.
• Limits get documented as carefully as capabilities. If a claim is not measured, it does not get made.

An issue on the relevant repository is the fastest route to me.