microsoft / microsoft/winget-cli
Provide some user defined or computed metric about the package maintainability
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
As I navigate to the list of packages at https://github.com/microsoft/winget-pkgs/tree/master/manifests I find a very wide range of maintenance policies. From packages which are updated automatically from upstream and others which where packaged once and are no longer maintained upstream.
From a security/risk perspective as a user I would like to understand what is the maintenance policy/status of a given package before installing it.
Proposed technical implementation details
Option a) Require maintainers provide/revalidate such detail as metadata - hard/costly to maintain
Option b) Compute some maintainability status based on the package age, delta to latest version, etc
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 comparing the two proposed approaches: maintainer-provided metadata versus a computed status based on package age and version differences. Review how package metadata, versions, and upstream updates are represented in the repository. Done would require an agreed definition of maintainability and a concrete implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100