Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

Public monitor/status/health board for @npm/cli-team's maintained projects

License

NotificationsYou must be signed in to change notification settings

Shivam7-1/statusboard

 
 

Repository files navigation

npm.github.io/statusboard

A single view to help monitor the status/health of the@npm/cli teams's Open Source Projects.

Data

Adding a project

GitHub search query fororg:npm topic:npm-cli fork:true

To be included here a repo must be in thenpm org and have thenpm-cli topic added to it. The data is rebuilt daily so the repo should appear by the next day.

Repos are also searched for workspaces via thepackage.json#workspaces array and those are included if they do not havepackage.json#private.

Removing a project

Projects are removed from the list if they are archived on GitHub and deprecated on the npm registry, or if they are archived and moved to a workspace of another repo we track. The topicnpm-cli does not need to be removed and should be kept on GitHub repos for historical reference.

Developing:

To update maintained projects:

Locally:npm run fetch:maintained -w data

CI:gh workflow run fetch-maintained.yml

To update daily data:

Locally:npm run fetch:data -w data

CI:gh workflow run fetch-data.yml

Serve / Publish Site

Serve:npm run dev -w www

Publish: The site is published to GitHub Pages on all pushes tomain.

Forking

This project aims to have some portability, but it will not work out-of-the-box if forked. Here are the things we're aware of that you should change if you fork this:

  • Enable the GitHub Action workflows after forking. They are not enabled by default on forked repos
  • Update misc links and references to your org
  • Delete all historical data fromworkspaces/www/lib/data/**/*.json
  • Update the necessary config items in:
  • Have aAUTH_TOKEN=${{ GITHUB TOKEN}} inworkspaces/data/.env if you are fetching data locally. All the data here is from open source repos and packages on the npm registry. So if you're data is private this token will need to have the proper scopes. You can look indata/lib/api/ to see all the calls that are made.
  • Runnpm run fetch:maintained -w data andnpm run fetch:data -w data to populate your new data

About

Public monitor/status/health board for @npm/cli-team's maintained projects

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript91.8%
  • CSS6.0%
  • HTML1.2%
  • Handlebars1.0%

[8]ページ先頭

©2009-2025 Movatter.jp