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

squatter

v0.2.1

Published

Check if a namespace on npm is being hogged.

Downloads

69

Readme

squatter Build status for Squatter Build status for Squatter on Windows

Check if a namespace on npm is being hogged.

Why?

  • Find out if a package name is worth disputing.
  • Filter out low quality packages in tools (e.g. search).
  • Check the quality of your own packages.

Install

npm install squatter --save

Usage

Get it into your program.

const squatter = require('squatter');

Check whether a given package name is being squatted.

squatter('foo').then((isSquatted) => {
    console.log(isSquatted);  // true
});
squatter('build-path').then((isSquatted) => {
    console.log(isSquatted);  // false
});

Algorithm

A heuristic is used to determine if a package is a squatter.

A squatter is a package that is not either exempt, useful, or high quality.

Packages are guilty until proven innocent.

Exemptions

A package is exempt (aka not a squatter) if it has at least one of:

  • A new version was published within the last 30 days
  • Significant download activity

Usefulness

A package is useful (aka not a squatter) if it has all of:

  • A README that is at least 100 characters long
  • Has a binary or is depended on by another package
  • Its version is 1.0.0 or higher

Quality

A package is high quality (aka not a squatter) if it has at least 80% of:

API

squatter(name)

Returns a Promise for a boolean of whether the name is being hogged on npm, as determined by the algorithm.

name

Type: string Example: build-path

Any valid npm package name.

CLI

See squatter-cli to use this on the command line.

Contributing

See our contributing guidelines for more details.

  1. Fork it.
  2. Make a feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request.

License

MPL-2.0 © Seth Holladay

Go make something, dang it.