npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@school-as-code/school-as-code-package

v1.0.5

Published

NPM package to automate the learning space of school-as-code

Downloads

7

Readme

School as Code: NPM package

This is the package used in the GitHub actions to set up the School As Code template repository.

Why an NPM package?

  • it can be used to set up the repository locally
  • it can be run by an action to set up the repository with one click
  • easier to develop than an action

In the Bin

  • /avatars.js: Fetches and saves the GitHub avatar for each learner into the .school/assets/avatars folder. These are used in the rendered README.
  • /collaborators.js: Adds each learner as a collaborator in the repository.
  • /full-setup.js: Does all of these things. Does not render the README until after the projecting is setup, it needs board and milestone numbers to render the README.
  • /projecting.js: Setups up a project board, creates configured labels, and one milestone per material. It persists an updated config with the milestone and board numbers added (this is used to render the README).
  • /render-readme.js: Renders a README with the configured materials, learners, and links filtering over repository issues & project board.