Find a way to detect unmaintained modules
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 354
- Avg merge
- 10h 18m
- Merged PRs (30d)
- 12
Description
We could find a way to calculate a score based on some factors to know if a module is actively maintained or not.
Ex:
- GitHub issues without answer from a maintainer
Any feedback welcome
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
The issue names no implementation files, tests, or entry points. First clarify which module data and maintenance signals are available, then define the scoring approach and acceptance criteria with maintainers; done means an agreed, actionable scope rather than an open-ended proposal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100