Expand some statistics to the ecosystem packages
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 0
- Avg merge
- 9h 25m
- Merged PRs (30d)
- 3
Description
To emphasize the size of the community, we could expand some of the stats to all ecosystem packages:
At least
- number of contributors
- number of citations
- number of stars
But basically we could do this for all metrics that don't have a too high API burden and then aggregate later by core / ecosystem as we see fit.
Contributor guide
No contributing guide indexed for this repository
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 files or tests are named. Start by locating the existing statistics collection and aggregation entry points, then assess which ecosystem-package metrics can be collected within the API burden. Done means contributor, citation, and star counts are included for ecosystem packages, with results separable into core and ecosystem groups.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100