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

worstpractices

v0.0.1

Published

WorstPractices.js -- A library to cause all the problems you didn't know you had

Downloads

14

Readme

worstpractices

WorstPractices.js -- A library to cause all the problems you didn't know you had

I know the repo should have a hyphen if I wanted to refer to it as WorstPractices and not Worstpractices, but that would be a best practice.

MISSION

Does your app have dependencies? Do you worry about them causing problems?

What if you could make those problems happen now?

Introducing WorstPractices.js, a library that will try its best to reversibly break your app.

Inspired by Netflix's Simian Army and finally motivated by this delightful chain of events, this library will gradually add some JS and NPM-related scripts that can ideally raise weaknesses or vulnerabilities in your code/build. When you feel like testing the resiliency of your app, you can either try a specific script to see the damage, or let WorstPractices choose a random one for you.

Also, if I see an opportunity for this repo to update in a way that can highlight weaknesses (other than unpublishing the repo), I'll do that and mention it in the changelog or release notes. So lock your version number or get ready for a Wild Ride.

CONTRIBUTION

Since there are countless unknown ways your app might screw up (and I'm only one person), I'm hoping to build this library with the help of the JS & Node community.

Here are the only rules I currently have for contributions:

  • They must not cause any irreversible damage to an app's code or build (no rm -rf, except maybe inside /node_modules)
  • They must highlight a weakness or vulnerability that is worth finding (leave the style linting to the linters)
  • They try to follow the Node Contribution Guidelines. This library is already designed to be frustrating, so we might as well keep the community around it as light-hearted as possible.