Is Powershell Lsp safe and trustworthy?

tashan scores Powershell Lsp on public evidence — tashan score 50.0/100, it is currently active. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Powershell Lsp?

Configure it from its source repository — it is a remote / registry server.

Who maintains Powershell Lsp?

source: manderse21/claude-powershell-lsp.

‹ The Index

Powershell Lsp

plugin

Real-time PowerShell diagnostics in Claude Code: as Claude edits a .ps1/.psm1/.psd1, it runs PowerShell Editor Services + PSScriptAnalyzer over that file and surfaces syntax errors and lint fixes inline. Hover, go-to-definition, and find-references serve natively through an opt-in handshake shim (userConfig nativeServe, off by default).

Works with: Claude Code (native)
native: this artifact type is that client's own format

Category: Dev Tools & CI — see all ranked ›

Install (Claude Code):

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

tashan score: 50.0
Adoption: 1 repos
Freshness: 100.0
Evidence coverage: 59% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
GitHub stars: 5
License: GPL-3.0

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Powershell Lsp scores 50 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down — and tells you the day it moves.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/plugin-manderse21-claude-powershell-lsp-powershell-lsp.svg)](https://tashan.sh/capability/plugin-manderse21-claude-powershell-lsp-powershell-lsp.html)

source ↗ · plugin:manderse21/claude-powershell-lsp/powershell-lsp

Everything on this page is public evidence and free. What it cannot know is whether you run this — npx tashan-cli doctor reads your own config and names what is wrong in it, also free. tashan Pro tells you the day any of it changes.

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-14 · scorer s5 · how · something wrong here?