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

npm-owned-modules

v0.1.7

Published

Get the list of npm modules owned by a user.

Downloads

18

Readme

npm-owned-modules Build Status

Get the list of npm modules owned by a user.

about it

Since npm doesn't publish any docs for interacting with their API, the best you can do is read through their website repo and try to reverse engineer it.

What I found was that it's just a simple HTTP call which returns a JSON array of modules.

So keep using this module if you want, or just hit up this URL:

https://registry.npmjs.org/-/user/USERNAME/package

Where USERNAME is obviously the users name, like saibotsivad.

Additional GET query params are possible:

  • per_page: Number of results to include on paginated query.
  • page: Zero-indexed page for paginated results.
  • format: Changes the amount of data returned. As best as I can tell the only options are not using it or the string mini.

For example, to get 5 modules from the user saibotsivad go here (even in your browser):

https://registry.npmjs.org/-/user/saibotsivad/package?per_page=5&page=0

That's it.

using this module

Install it the normal way:

npm install npm-owned-modules

You just call it with a string that's the user name:

var ownedModules = require('npm-owned-modules')
ownedModules('saibotsivad', function(err, modules) {
	// modules array
})

The modules list is just a simple array of module name strings, e.g.:

var modules = [
	'npm-owned-modules',
	'ftp-core'
	// etc.
]

license

VOL