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

swizzy

v2.2.0

Published

[![ESLint](https://img.shields.io/badge/code_style-eslint-4B32C3.svg)](https://eslint.org) [![TypeScript](https://img.shields.io/badge/built_with-typescript-3178C6.svg)](https://www.typescriptlang.org)

Downloads

15

Readme

swizzy

ESLint TypeScript

Swizzy is a pretty formatter for SwiftLint output. It transforms SwiftLint's standard output into a more readable and stylish format. This project is inspired by snazzy.

JavaScript Style Guide

Features

  • Formats SwiftLint output in a compact and stylish way
  • Written in TypeScript for better maintainability and type safety
  • Easy integration with existing SwiftLint workflows
  • Customizable output formatting
  • Works seamlessly with CI/CD pipelines

Installation

npm install -g swizzy

Make sure you have SwiftLint installed:

brew install swiftlint

Usage

Swizzy can be used in two main ways:

  1. Piping SwiftLint Output (Recommended):

    Run swiftlint with the --reporter json flag and pipe the output directly to swizzy. This is the most reliable method.

    swiftlint lint --reporter json | swizzy
  2. Automatic SwiftLint Execution:

    If you run swizzy without any piped input, it will attempt to execute swiftlint lint --reporter json automatically for you. Note: This requires swiftlint to be installed and accessible in your system's PATH.

    swizzy

Options

  • --help, -h: Show help message.
  • --version, -v: Show version number.
swizzy --help
swizzy -v

Example in package.json

You can integrate swizzy into your npm scripts:

{
  "scripts": {
    "lint": "swiftlint lint --reporter json | swizzy"
  }
}

Then run npm run lint.

Screenshot

JavaScript Style Guide

Development

To contribute to swizzy, clone the repository and install dependencies:

git clone https://github.com/yourusername/swizzy.git
cd swizzy
npm install

Available scripts:

# Build the project
npm run build

# Run tests
npm test

# Lint code
npm run lint

# Fix linting issues
npm run lint:fix

Testing

To run the basic test case included in the repository (which uses a predefined anonymized JSON file):

cat anonymized_lint.json | node dist/index.js

Contributing

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -am 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

License

MIT