You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Objective: PSModule modules are the best-maintained on the Gallery
Modules published through the PSModule framework should be exemplars of quality on the PowerShell Gallery β well-documented, consistently versioned, actively maintained, and trustworthy.
Key Results
KR1: Documentation coverage β Every published module has generated API documentation, a populated README, and a live documentation site
KR2: SemVer discipline β Zero unintentional breaking changes reach the Gallery (every major bump is deliberate, labeled, and documented)
KR3: Freshness β Modules with active development publish at least once per quarter; dependency updates are applied within 30 days
KR4: Quality gates β All published modules pass PSScriptAnalyzer, framework tests, and meet their code coverage target
What "best-maintained" means
Users can trust that a new version won't break their scripts (SemVer is real, not aspirational).
Documentation is always current β generated from source on every release.
Dependencies are tracked and updated, not left to rot.
The Gallery page has an icon, a description, release notes, and links to docs.
Issues are triaged, PRs are reviewed, and abandoned work is cleaned up.
Initiatives (linked as sub-issues)
Initiatives that move these KRs will be added as sub-issues below.
Objective: PSModule modules are the best-maintained on the Gallery
Modules published through the PSModule framework should be exemplars of quality on the PowerShell Gallery β well-documented, consistently versioned, actively maintained, and trustworthy.
Key Results
What "best-maintained" means
Initiatives (linked as sub-issues)
Initiatives that move these KRs will be added as sub-issues below.