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

stegomark

v2.0.1

Published

A program that hides images in images - basic, yet robust

Downloads

7

Readme

stegomark

A package for watermarking images with images with LSB. (currently only works with pngs)

How to use

var stego = require('stegomark')
stego.write("in.png", "write.png", "out.png", {
  "callback": function () {
    stego.read("out.png", "extracted.png")
  }
})

Functions

stego.write(in_path, watermark_path, out_path[, options])
stego.read(in_path, extracted_path[, options])

Options

  • callback: to be called when the output image write is finished
  • squeeze_protection: only on write - integer - the higher this integer, the more resistance to resizing

How it works

The image watermark is rounded to 3-bit color - enough to fit in the LSBs of R, G, and B

For example, if we wanted to watermark the pixel with color FEB101 (orange) with another pixel of color FF006E (pink), the program would:

  1. Round the color to be watermarked Essentialy, it divides the value of each color channel by 255, rounds to the nearest integer, and reconcatenates. This process results in a 3 bit color of 100, which expanded to 24 bit is FF0000 i.e. red
  2. Take the 3 bit color and put it in the lowest bits of each channel of the original image. This results in a new color of FFB000 (very slightly different orange)
  3. Repeat for all the watermark pixels

Reading does this in reverse.

Why is this better?

  1. In other LSB implementations, data stored in individual pixels is dependent on data from other pixels. However, by sacrificing color quality, we can store small, independent groups of data
  2. (my opinion) I like the visual system more - rather than extracting a cryptic message, one can show the message in a visual form.

Example!

The input image below:

In

Was watermarked with this and a squeeze protection of 5:

Write

And created this output image:

Out

That had this data:

Extracted

Testing against squeezing

I squeezed the output image in paint.net to get this:

In-squeeze

But I was still able to extract this image:

Extracted-squeeze