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

pixellint

v0.30.3

Published

Validator for pixels, postbacks, conversion API payloads, and tracking URLs: Meta CAPI, Facebook pixel, GTM, and vendor rulepacks

Readme

pixellint

Validator for pixels, postbacks, conversion API payloads, and tracking URLs, as a WASM-backed npm package. Same engine, same rule ids, and same evidence levels as the pixellint CLI. Paste a URL or a CAPI JSON body at pixellint.org.

npm install pixellint
import { validate, isOk, validateMany } from "pixellint";

const pixel = validate("https://www.facebook.com/tr?ev=Purchase");
isOk(pixel); // false: missing Pixel ID

const capi = validate(
  JSON.stringify({
    data: [{ event_name: "Purchase", event_time: 1770000000000, action_source: "website" }],
  }),
  { kind: "json" },
);
isOk(capi); // false: event_time is milliseconds, Meta wants seconds

const document = validateMany([
  "https://example.com/pixel?id=1#frag",
  "https://example.com/pixel?id=1#frag",
]);
document.summary.unique_artifacts; // 1

Every finding carries a stable code, a severity, a fix_hint, the byte range it applies to, and the document it came from:

const [finding] = pixel.reports.flatMap((report) => report.violations);

finding.severity;         // "error"
finding.source.level;     // "official_vendor"
finding.source.reference; // "https://developers.facebook.com/docs/meta-pixel/get-started"
finding.targets[0];       // { component: "whole_url", start: 0, end: 46, ... }

What it checks

  • URL conformance, transport, credentials, fragments, and ad-tech macro handling
  • IAB consent signals: TCF gdpr and gdpr_consent, the deprecated US Privacy string, and GPP gpp and gpp_sid
  • Vendor parameter contracts for 129 endpoint families, including Meta Conversions API, TikTok Events API, Reddit CAPI, and the browser pixels
  • Endpoint attribution for 119 vendor rows, so an unrecognized pixel still gets a name.

API

| Function | Returns | | --- | --- | | validate(artifact, options?) | The full validation summary | | validateMany(document) | Document report for extracted artifacts | | isOk(summary) | false when any error-severity finding is present | | rulepacks() | Every rulepack with its evidence level | | vendors() | The vendor endpoint directory | | vendorForHost(host) | The vendor that serves a host, or null | | version() | The pixellint-core version this build wraps |

options takes kind (url by default, plus json, vast, postback, request, unknown), state (unknown, template, fired), and vendor for a caller's claimed vendor. html, js, and gtm throw: extract URLs first.

Templates keep their macros: pass { state: "template" } and unexpanded macros stop being findings.

Links

Apache-2.0. Not affiliated with any vendor named in its rulepacks.