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

eslint-plugin-prototype-pollution-security-rules

v1.0.6

Published

Detect the use of vulnerable features within some libraries from https://github.com/HoLyVieR/prototype-pollution-nsec18/ that are not yet fixed

Downloads

65,532

Readme

Prototype Pollution Security Rules For ESLint

These rules are to supplement the security issues documented by Oliver Arteau at https://github.com/HoLyVieR/prototype-pollution-nsec18 some of the issues have not been resolved by the maintainers.

NPM

The main reason for these rules, is because npm audit does not report that certain libraries have known problems:

NPM

ESLint

These rules will atleast tell you if vulnerable features are being utilized

ESLint

Usage

If you want to scan this against your code bases, you can through the following:

  • Install the rule locally or globally such as npm install eslint-plugin-prototype-pollution-security-rules
  • Add the rule to your .eslintrc
    • Inside plugins add detect-prototype-pollution
    • Inside rules add "detect-prototype-pollution/detect-merge": 1
    • (full list below)

Example:

ESLint Config

Rules

Current rules are:

  • detect-merge - link and link
  • detect-merge-objects - link
  • detect-merge-options - link
  • detect-deep-extend- link