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 🙏

© 2024 – Pkg Stats / Ryan Hefner

mapzen-search-team-ownership

v1.0.1

Published

manage npm owner status in bulk

Downloads

3

Readme

ownership

This is a module template for the npm owner command to make management of open source projects with many contributors easier, by keeping specific lists of users with access and optionally packages they should have ownership of.

This doesn't bend any laws you need to be an owner of the package yourself in order to add other owners, just like you would using npm owner.

FORK ME

This is a template, not a finished project. It is meant for you to copy & rename. For instance, at Mapbox, we have a copy called mapbox-owners that adds all employees to a package. It's called mapbox-owners and has a hardcoded list of people in the package: updating the package updates the list.

Do the same: fork this, rename it in package.json to something else, change the names of the binaries, and change the example-users.json and example-packages.json configuration files to suit your fancy.

install

npm install -g ownership

usage

Provides two utilities:

ownership

ownership: takes one argument, the name of the package, and adds all users to that package as owners. For instance:

ownership express

Would add all users in example-users.json as owners to the express package.

ownership-all

ownership-all doesn't take any arguments: it adds all users in example-users.json to all packages in example-packages.json.

ownership-rm

ownership-rm takes one argument, the name of a user, and removes that user from all of the packages in example-package.json. For instance:

ownership-rm misspelled-name

Would remove misspelled-name as owner from all the packages in example-package.json.