PowerShell / PowerShell/PSScriptAnalyzer
Add version to PSScriptAnalyzer assemblies
Open
Nobody has claimed this yet.
Area - Build
Issue - Enhancement
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
For Authenticode signing, having reliable version metadata can help with policy rules. We should add this data from something like a common props file for PSSA releases to allow use with locked-down environments
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 locating the build configuration or common props file used for PSScriptAnalyzer releases and inspect how assembly version metadata is currently defined. The work is done when the released assemblies expose reliable version data suitable for Authenticode policy rules; no specific test or entry point is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- build-system, release, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100