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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@andyrmitchell/securethis

v0.0.4

Published

Run static security scans on your project's code base.

Readme

@andyrmitchell/securethis 🛡️

A CLI tool that performs security scans on your codebase using popular SAST engines (e.g. Fluid Attacks).

⚠️ Prerequisites

Before you can use securethis, you must have Docker installed and running on your system.

📦 Installation

Install secureThis as a development dependency in your project:

npm i -D @andyrmitchell/securethis
# or
yarn add --dev @andyrmitchell/securethis

🚀 Usage

Once installed, you can run security scans on your project by executing the following command from your project's root directory:

npx securethis

The first time it runs it'll create a config file next to package.json, called securethis.config.ts; and ask you to run it again.

The npx securethis command will:

  1. Check for Docker.
  2. Pull the necessary Docker image(s) for the scanners (if not already present).
  3. Mount your current working directory (your codebase) into the Docker container.
  4. Execute the security scan(s).
  5. Display the results in your console.

Recommendations

  • Add it to your build process as an initial step

⚙️ Configuration

You can edit securethis.config.ts in your project root. (Can't see it? Run npx securethis and it'll be created then halt before executing any scans.)

E.g. you can edit the output directory, and what files are excluded.

🔬 Supported Scans

securethis currently supports the following types of scans:

### FluidAttacks (SAST - Static Application Security Testing)

  • Description: Analyzes your source code without executing it to find potential security vulnerabilities, such as SQL injection, XSS, insecure configurations, and more.
  • Engine: FluidAttacks Scanner
  • How it works: It loads in Docker and creates a virtual (read only) mapping to your project (by dynamically creating a yaml config file from its internal base-fluid-attacks-config.yaml and securethis.config.ts in your project root).

📄 Output & Reports

Scan results, including identified vulnerabilities and their locations, will be printed directly to your console.

🛣️ Roadmap

  • [ ] Support for more SAST engines
  • [ ] Consider support DAST engines
  • [ ] Software Composition Analysis (SCA) for vulnerable dependencies.
  • [ ] Secret scanning
  • [ ] CI/CD integration guides and examples

🔧 Troubleshooting

  • Docker command not found or Cannot connect to the Docker daemon:
    • Ensure Docker is installed correctly and the Docker daemon/service is running.
    • You might need to start Docker Desktop or run sudo systemctl start docker (on Linux).
  • Scan fails unexpectedly:
    • Check the console output for specific error messages from the underlying scanner.

📝 License

This project is licensed under the MIT License - see the LICENSE.md file for details.