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 🙏

© 2025 – Pkg Stats / Ryan Hefner

scandal-cli

v0.1.0

Published

Atom's Scandal search on the command line

Downloads

17

Readme

scandal-cli

A simple command line interface to scandal

screenshot

install

npm install -g scandal-cli

usage

scandal <search pattern> [<path pattern>]

It will search recursively down from the directory it was invoked from

search pattern

The term you are searching for. It will get converted into a regexp so regexp operators are ok. Depending on what the term is, you may need to wrap it in quotes so the shell doesn't mess with it.

The search term is case sensitive.

path pattern (optional)

A pattern of paths to include, globbing and regexp operators are supported, each path is separated by a comma.

To exclude paths, prefix them with ~

The examples section should make everything clear.

examples

search for either "let" or "var" in all files except in node_modules

scandal "(let|var)" ~node_modules

search for ghost in all JavaScript files

scandal ghost "*.js"

search for "allresults" or "allResults" in src/foo and src/bar, but not src/baz

scandal "all[r|R]esults" src/foo,src/bar,~src/baz

search for "monkey" in all JavaScript demos

scandal monkey "**/__demos__/**/*.js"

search for kitty in all JavaScript source files but skip tests

scandal kitty *.js,~__tests__

Tested on

A Linux box using bash and node 6.4.0.