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

@alexbainter/file-icons

v1.0.0

Published

Icons from the file-icons project

Readme

File Icons

This is the source for the File Icons project's custom icon-font.

Please submit a request if an icon is missing.

“Why request an icon? Can't I submit a PR?”

You can. But your submission will end up getting overwritten.

Everything in the svg directory is meticulously optimised by hand, so that each icon contains as few control-points as possible:

Icon optimisation example, taken from DevOpicons readme

This task requires time, patience, and above-average aptitude with image editing software. Even if you have all three, I still have to check the SVG file myself; both our lives are made easier by simply linking to where the icon can be found. Failing that, you can use a fenced code-block to embed the SVG in the issue itself:

<details>

```svg
<!-- Replace this with the contents of your SVG file. -->
```

</details>

Note: The empty line separating <details> from its content is required. Refer to the CommonMark spec for the gory details of HTML handling in Markdown.