nodejs / nodejs/package-maintenance

Impactful Projects Statusboard

Open
#569 6 comments 0 reactions 1 assignee View on GitHub

@darcyclarke is already working on this.

Since Jul 18, 2023.

Dominant language
No language data
Stars
423
Forks
147
PR merge metrics
No merged PRs in 30d

Description

Description

This group defined a number of projects/goals for 2023 & one of them was to create a new "statusboard" (similar to npm's projects statusboard) to help track the state/number of "popular"/"impactful" packages (scope yet to be defined). I will be championing the initial work with a deadline for completion being the Open Source Summit EU Conference in Bilbao September 19-21st (undefined end-date/ongoing/WIP).

Todo:
Initial Proposed Columns
  • Name
  • Repo link
  • Package link
  • CI/Build status of default branch
  • # of PRs
  • # of Issues
  • # of Unlabelled Issues
  • Package Version
  • Node Version (if defined)
  • License
  • Last Commit Date
  • Last Published Date
  • # of Stars
  • # of Downloads
  • # of Maintainers
  • # of Contributors
  • # of Versions
  • # of Vulnerabilities (CVEs)
  • OpenSSF Scorecard
  • Socket Scorecard
  • Is in CITGM? (Boolean)
  • Has Types? (Boolean)
  • Type of Module (ESM/CJS/Duel)
  • Deprecation Status (Boolean)
  • Funding field defined (ex. GitHub Sponsors funding.yml or package.json.funding)
Updates
  • @darcyclarke to merge "top 500 downloads" & "top 500 depended" package lists to generate initial "impact" list/scope

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.