PSScriptAnalyzer
PowerShellEditorServices
PSScriptAnalyzer | PowerShellEditorServices | |
---|---|---|
15 | 5 | |
1,781 | 598 | |
1.0% | 0.8% | |
7.4 | 9.1 | |
7 days ago | 7 days ago | |
C# | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
PSScriptAnalyzer
-
Using PSScriptAnalyzer to check PowerShell version compatibility - Building custom compat profiles
I am looking to build a custom profile for a ws2019 with ps 7.2 + to use to check my scripts, i have tried using the compat collector https://github.com/PowerShell/PSScriptAnalyzer/tree/development/PSCompatibilityCollector and running the build.ps1 script there but I do not see an output for my commands and the script text doesn't provide much clarify to me at least.
-
What open source tools do you use to check the security of your PowerShell scripts?
PSScriptAnalyze is a static code analysis tool that checks PowerShell scripts for best practices and potential security issues. It is available on GitHub and can be installed as a module in PowerShell. https://github.com/PowerShell/PSScriptAnalyzer
-
PSScriptAnalyzer
PSScriptAnalyzer is a static code checker for PowerShell modules and scripts. Runs a set of rules that test the quality of PowerShell code against best practice, then warns about potential code defects and suggests potential solutions. xXxLinuxUserxXx likes this linter "to get unified codestyle in the scripts."
-
I made a Dell Command Script for Intune, thought others may find it helpful.
Not a windows admin and more like a programmer but i would suggest to use some linter (https://github.com/PowerShell/PSScriptAnalyzer) to get unified codestyle in the scripts :)
-
Azure Guest Invitation
It’s best practice to keep $null on the left side of comparisons https://github.com/PowerShell/PSScriptAnalyzer/blob/development/RuleDocumentation/PossibleIncorrectComparisonWithNull.md
- Dangerous and Insecure PowerShell Code in the Enterprise
-
Smarter autocomplete
This one is a real problem. When I reference a type which is defined in another file in a class, I get an error in my vscode. the class works but the PSScriptAnalyzer doesn't know that the type is imported. I found this github issue which is about supressing the issue, I tried that and couldnt get it to work but I'd rather that it just recognized the type from the other file https://github.com/PowerShell/PSScriptAnalyzer/issues/1041
-
Who uses Visual Studio Code for PowerShell Scripting?
I would definer not autoformat on save with bugs such was this still outstanding: https://github.com/PowerShell/PSScriptAnalyzer/issues/1580
-
help with add-newuser profile names
That's some sloppy code. Wmic is deprecated. You shouldn't put unencrypted passwords in scripts. You shouldn't use write-host anymore. $null goes in front, etc. Try using https://github.com/PowerShell/PSScriptAnalyzer to ensure decent code. Also write code in vscode. Also read https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.localaccounts/new-localuser?view=powershell-5.1
-
Module workflow in VS Code?
I discovered the Invoke-Build build system, PSScriptAnalyzer for linting, and Pester for testing/mocking. I wrote a GitLab CI/CD pipeline that takes advantage of all of this to push releases to our company's PSRepo. I also discovered the Plaster template system for scaffolding new projects, and created a custom company template for standardizing our repo structures.
PowerShellEditorServices
-
PowerShell Extension for Visual Studio Code July 2022 Update
Yep! A bit light. Andy has been focusing hard on regression tests (which were unfortunately very lacking previously) and most of my work has been on syncing breakpoints between the UI and the console outside of debug sessions (a lot more work than it sounds like, see this work in progress PR).
-
LSP and PowerShell
I noticed that PowerShell is supported through LSP and that the PowerShell extension in Visual Studio Code uses it. (PowerShellEditorServices)
-
PS Development software
Sure, PowerShellEditorServices (the thing that enables the terminal inside VSCode and does tab-completion/Intellisense) isn't perfect and it sometimes throw a bunch of errors if I resize the window. I mainly use VSCode for its extremely good extensions. Oh, and autosave.
- Why is PowerShell tab completion so awful in vscode?
-
Please HELP: Neovim Built-in --> how to add powershell language server [and break my coc addiction]
Sadly I have to be on windows: I need this: https://github.com/PowerShell/PowerShellEditorServices
What are some alternatives?
Pester - Pester is the ubiquitous test and mock framework for PowerShell.
coc-powershell - PowerShellEditorService integration for coc.vim
vscode-powershell - Provides PowerShell language and debugging support for Visual Studio Code
python-language-server - Microsoft Language Server for Python
PSReadLine - A bash inspired readline implementation for PowerShell
PSRule - Validate infrastructure as code (IaC) and objects using PowerShell rules.
nvim-lsp-installer - Further development has moved to https://github.com/williamboman/mason.nvim!
csharp-language-server-protocol - Language Server Protocol in C#
ImportExcel - PowerShell module to import/export Excel spreadsheets, without Excel
haxe-language-server - Language Server Protocol implementation for the Haxe language
jtbl - CLI tool to convert JSON and JSON Lines to terminal, CSV, HTTP, and markdown tables
libxo - The libxo library allows an application to generate text, XML, JSON, and HTML output using a common set of function calls. The application decides at run time which output style should be produced.