PowerShell / PowerShell/PSScriptAnalyzer
UseFullyQualifiedCommandNames: Implement a rule to flag command uses that could be ambiguous based on state
Open
Nobody has claimed this yet.
Area - Rules
Consider - 2.0
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Without fully qualified command invocation there are various ways to plant another command. We should advise PowerShell users to use the correct pattern.
ways to plant:
- aliases
- native command in path
- loading another module with a command with the same name
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
No file, test, or entry point is named. Start by defining how the rule should identify unqualified command uses that may be affected by aliases, native commands in PATH, or commands loaded from another module; done should include clear guidance to use fully qualified command invocation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- security, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100