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

poppins-exec

v0.1.0

Published

mary-poppins plugin for running a local command

Downloads

3

Readme

poppins-exec Build Status

A Mary Poppins plugin for running local commands in response to GitHub comments.

Note: depending on how you configure this plugin, it may be exploitable. As a best practice, you should run mary-poppins as an unprivileged user.

Install

npm install poppins-exec

Configure

To use this plugin, you need to load it in your config file with couldYouPlease:

// config.js
module.exports = function (poppins) {

  // load the plugin
  poppins.couldYouPlease('poppins-exec');

  // configure it
  poppins.plugins.exec = {

    // regexs to match against and the corresponding script to run in response
    commands: [
      { re: /^\s*LGTM\s*$/, exec: 'echo "merged!"' }
    ],

    // users to respond to
    owners: [ 'btford' ]
  };
};

Security

I think there may be a case where someone with write access to the repo could edit your comment body before mary-poppins reads and parses it so I suggest only running this on repos that you own.

Be careful how you use this, or you'll subject yourself to shell injection.

Your best bet is to only use very specific input as parameters like:

  • a number: ([0-9]+)
  • a string of alphanumeric characters: ([a-zA-Z]+)

License

MIT