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

ai-nevermore

v0.1.2

Published

Nevermore =========

Readme

Nevermore

Nevermore is a library to obfuscate media on the web to prevent AI scraping.

The following table is a matrix of potential techniques and media:

| | Random Poison | Targeted Poison | Obfuscation | Encryption | |--------------|----------------|-----------------|---------------|------------| | Text | Nevermore | Nevermore[TBD] | Nevermore | | | Image | | Nightshade | Nevermore | | | Video | Nevermore[TBD] | | Nevermore[TBD]| | | Audio | | HarmonyCloak | | | | 3D Models | Nevermore[TBD] | | Nevermore[TBD]| | | Code | Nevermore[TBD] | | | |

There are conceptually 2 other techniques to fight AI.

  1. Scrape traversal traps: dynamically generated nonsense hierarchy of pages to indefinitely trap the scraper on your site. It incurs additional hosting costs, but gives the possibility of being blacklisted by the scraper. Examples of this include Nepenthes and Iocaine
  2. Scrape Poison: This technique exploits weaknesses in the scrape engines or or selector format to prevent scraping of the correct data. This is currently only theoretical, but is something we are looking at.

Text

while a user will see

original text

A scraper coming to your site will see something like

encoded text

Which will both prevent the scraper from acquiring your content as well as poisoning the model trained from it.

Images

First you encode an image with:

nevermore pseudoimage <target> --image-output <output> --encode

which produces and encoded image, seemingly static filled.

Then you include the encoded image along with it's key(This uses the source directly, but it is also is compatible with your favorite build tool) the stub entries must point at any valid ESM file and are not used.

<html>
    <head>
        <script type="importmap">
            {"imports":{
                "node:os":"<path-to-stub>",
                "node:stream":"<path-to-stub>",
                "fs":"<path-to-stub>",
                "os":"<path-to-stub>",
                "module":"<path-to-stub>",
                "nevermore/encoded-image":"./node_modules/nevermore/src/encoded-image-component.mjs",
                "@environment-safe/canvas":"./node_modules/@environment-safe/canvas/src/index.mjs",
                "@environment-safe/file":"./node_modules/@environment-safe/file/src/index.mjs",
                "@environment-safe/elements":"./node_modules/@environment-safe/elements/src/index.mjs",
                "@environment-safe/runtime-context":"./node_modules/@environment-safe/runtime-context/src/index.mjs"
            }}
        </script>
        <script type="module">
            import 'nevermore/encoded-image';
        </script>
    </head>
    <body>
        <encoded-image src="encoded-image-location" key="VFYZT-HPTRG-PGHRT"></encoded-image>
    </body>
</html>

Markup

Nevermore can traverse and inline transform all text and image elements in an HTML body.

nevermore pseudomarkup <target> --unified-output <output location>

this puts imports, styles and image decodes all inline.

Programmatic Usage

This library can be used to generate the html and css:

import { computeIndexKeys, generateHTMLAndCSS } from 'ai-nevermore';

const { root, index } = await computeIndexKeys(inputText);
const { html, css } = await generateHTMLAndCSS(root, index);

You can programmatically encode/decode images:

const image = new NevermoreImage({
    url:'<target>',
    maskDir: '<texture_dir>'
});
await image.ready;
const canvas = image.encode();
await Canvas.save('./encoded.jpg', canvas);
const decoded = image.decode();
await Canvas.save('./decoded.jpg', decoded);

Command Line Usage

Install with npm install -g ai-nevermore

nevermore [command]

Commands:
  nevermore pseudotext [input-file]    transform text to poison
  nevermore pseudoimage [input-file]   transform XOR image encoding
  nevermore pseudomarkup [input-file]  transform html content

Options:
      --version            Show version number                         [boolean]
  -K, --key                key to use for decoding the image            [string]
  -U, --unified-output     File to generate html + css into             [string]
  -C, --css-output         File to generate css into                    [string]
  -I, --image-output       File to output image to                      [string]
  -H, --html-output        File to generate html into                   [string]
  -r, --raw-output         Do not wrap the ouput                       [boolean]
  -E, --encode             inline encoding                             [boolean]
  -D, --decode             inline decoding                             [boolean]
  -m, --render-mode        output mode
        [string] [choices: "fixed-mode", "inline-mode"] [default: "inline-mode"]
  -s, --size               The size of the font in pixels (required for
                           fixed-width)                   [number] [default: 12]
  -d, --custom-dictionary  A json map of replacement words              [string]
  -f, --font               The font in question (required for fixed-width; only
                           webfonts are supported)
      [string] [choices: "Andale Mono", "Arial", "Avenir", "Avenir Next", "Comic
  Sans MS", "Courier New", "Georgia", "Helvetica", "Impact", "Inter", "Times New
           Roman", "Trebuchet MS", "Verdana", "Webdings", "Open Sans", "Tahoma"]
                                                              [default: "Arial"]
      --help               Show help                                   [boolean]

Roadmap

  • [x] raw output mode
  • [x] stdin, stdout support
  • [x] custom dictionary
  • [x] image encoding
  • [x] web component decoder
  • [x] markup obfuscation
  • [ ] windows compatibility
  • [ ] self randomizing dictionary
  • [ ] add a replacement mode (opposed to a tokenizer based solution)
  • [ ] bindings
    • [ ] PHP CL binding
    • [ ] Python CL binding
    • [ ] Java CL binding
    • [ ] Ruby CL binding
  • [ ] native CMS Support
    • [ ] KeystoneJS
    • [ ] Ghost
    • [ ] Strapi
  • [ ] other CMS Support
    • [ ] wordpress
  • [ ] Framework Support
    • [ ] express
    • [ ] next.js
    • [ ] laravel
    • [ ] rails

Development

This release is currently unlicensed and should be treated as proprietary, but open meaning I am not currently accepting collaboration while I move toward 1.0 nor is this version of the code available for redistribution. I am currently evaluating source licenses for a future release during beta.

I am also looking for a robot license, should such a thing exist or some generous legal professional want to help in the creation of one.

Enjoy,

  • Abbey Hawk Sparrow