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

@unmarkk/cli

v1.0.5

Published

Command-line privacy-first watermark and metadata remover. Runs entirely on your machine.

Readme

@unmarkk/cli

Command-line unmark. Removes metadata from files on your machine, and never sends them anywhere.

npm install -g @unmarkk/cli
unmark inspect photo.jpg          # what does this file say about me?
unmark clean photo.jpg            # write photo.cleaned.jpg without it
unmark scan ~/Pictures --quiet    # which files in here are leaking?

No system tools required — no exiftool, no qpdf. Node 20.11+ and nothing else.

Commands

unmark inspect <path...>     Report what a file carries. Changes nothing.
unmark clean   <path...>     Write a cleaned copy.
unmark scan    <dir...>      Walk a directory and list files carrying metadata.
unmark clean report.docx --in-place            # overwrite, keeping a .bak
unmark inspect draft.md --stylometry           # include the writing-style heuristic
cat draft.txt | unmark clean - > clean.txt     # pipe through stdin
unmark scan ~/Documents --json | jq '.files[] | select(.flagged)'

Exit codes: 0 nothing found, 1 metadata found or signals survived a clean, 2 bad input or usage.

Run unmark --help for every option.

Safety

Writes are atomic — a temporary file in the destination directory, flushed, then renamed — so an interrupted run cannot leave a half-written document where the original was. Writes refuse to follow symlinks. --in-place takes a .bak copy before anything is overwritten.

License

MIT © Dhirender Choudhary