PowerShell / PowerShell/PSScriptAnalyzer
Contents of a Minimum ruleset
Open
Nobody has claimed this yet.
Area - Configuration
Area - Rule Sets
Issue - Discussion
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
I'll start with a list of some rules that probably should not be in a Minimum ruleset:
- PSAvoidUsingInternalURLs (vast majority of scripts are not distributed outside of orgs IMO)
- PSAvoidUsingComputerNameHardcoded (unnecessary for scripts not shared)
There are probably more rules than this that should be in a Minimum ruleset but this is just starting the conversation:
- PSUseDeclaredVarsMoreThanAssignments
- PSPossibleIncorrectComparisonWithNull
- PSAvoidUsingUserNameAndPassWordParams
- PSAvoidUsingConvertToSecureStringWithPlainText
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the current Minimum ruleset is defined and compare it with the rules listed in the issue, including the rules proposed for exclusion. Done means reaching an agreed scope for the ruleset; the issue does not name implementation files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100