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

@glomopay/secure-elements-sdk

v0.4.0

Published

Glomopay Secure Elements SDK — cross-origin iframe fields for collecting card data.

Readme

@glomopay/secure-elements-sdk

Cross-origin iframe fields for collecting card data. The SDK mounts hardened, sandboxed iframes served from a Glomopay-controlled origin; card data never touches the host page's DOM or JavaScript.

The package is published publicly to the npm registry under the @glomopay scope.

Install

pnpm add @glomopay/secure-elements-sdk
# or: npm install / yarn add

No registry configuration or authentication is required.

Usage

import { SecureElementsClient, ELEMENT_TYPE } from '@glomopay/secure-elements-sdk';

const client = new SecureElementsClient({ environment: 'production' });

const container = client.getElementsContainer();
const cardNumber = container.createElement({
  type: ELEMENT_TYPE.cardNumber,
  onChange: (state) => console.log(state.isValid),
});
cardNumber.mount('#card-number');

// later
client.destroy();

Environments

The iframe host is compiled in and selected by environment; callers pick from a fixed set and can never supply an arbitrary origin (this is what keeps the postMessage trust anchor intact).

| environment | Host | | ------------- | -------------------------------- | | production | production secure-elements host | | staging | staging secure-elements host | | development | development secure-elements host |

Every host is compiled in from a build-time env var (VITE_SECURE_ELEMENTS_HOST_STAGING, VITE_SECURE_ELEMENTS_HOST_PRODUCTION, VITE_SECURE_ELEMENTS_HOST_DEVELOPMENT); selecting an environment whose host is unset throws. development conventionally points at the portless alias secure-elements (https://secure-elements.localhost).

API

  • new SecureElementsClient({ environment }) — injects a hidden controller iframe and starts the inbound message gate. Must run in a browser.
  • client.getElementsContainer() — the client's single ElementsContainer.
  • container.createElement({ type, onChange?, onFocus?, onBlur?, onExternalErrorChange? }) — returns an IframeElement.
  • element.mount(selector) / element.unmount().
  • element.setError(message) / element.clearError().
  • client.destroy() — tears down every iframe and stops the listener.