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

@mhmdhammoud/leadcall

v0.1.0

Published

LeadCall shared libraries — a single package with namespaced subpaths (brand today; utils etc. in the future).

Readme

@mhmdhammoud/leadcall

LeadCall's shared libraries — a single npm package with namespaced subpaths. Today it ships brand; utils and others can be added later under the same package.

@mhmdhammoud/leadcall
└── brand/                       → import '@mhmdhammoud/leadcall/brand'
    ├── (colors, runtime exports)
    ├── logo.svg · logo.png
    ├── lottie/
    │   ├── loading.json   # ✅ idle loop — "call → signal → processing"
    │   ├── splash.json    # ✅ one-shot draw-on reveal — "reveal → brand"
    │   └── archive/blink.json   # ⛔ archived, not shipped to any surface
    └── video/                   # webm renders for marketing reuse
        ├── loading.webm · splash.webm
        └── archive/blink.webm

On disk these live under assets/brand/… and src/brand/…; the package exports map projects them onto the @mhmdhammoud/leadcall/brand/* subpath.

The two approved animations

| Variant | Meaning | Where it belongs | |---|---|---| | splash | Reveal → Brand | First app load, mobile startup, website hero, marketing/video intros, demo & launch assets. Plays once, freezes. | | loading | Call → Signal → Processing | Data/sync/processing waits: CRM sync, call-logs & analytics loading, background processing, empty states. Seamless loop. |

blink is archived — no product meaning for a B2B revenue-attribution platform, intentionally shipped nowhere. Kept only for reference.

Where NOT to animate: sidebar/header lockup, pricing, docs, legal, repeated SEO pages, every card, repeated page headers — use the static logo.svg.

Consuming it

npm install @mhmdhammoud/leadcall
// colors (compiled runtime export)
import { colors } from '@mhmdhammoud/leadcall/brand'
// colors.primary === '#10b981'

// Lottie JSON (imported straight from the package)
import loading from '@mhmdhammoud/leadcall/brand/lottie/loading.json' // lottie-react
import splash from '@mhmdhammoud/leadcall/brand/lottie/splash.json'   // lottie-react-native

The raw SVG is the one asset apps serve from a static URL path rather than importing, so npm run sync copies just logo.svg into each app (Next public/, Expo assets/). Everything else comes through npm.

Maintaining

npm run build     # regenerate Lottie JSON from logo.svg, then compile dist/
npm run release   # build + sync the SVG into consuming repos

Edit scripts/build-lottie-logo.mjs to change the animations (it parses assets/brand/logo.svg into Lottie bezier shapes — never hand-edit the generated *.json). Pushing to master runs CI (lint/typecheck/test) and publishes to npm.

Adding a new namespace (e.g. utils)

Add src/utils/ + assets/utils/, then two exports entries: "./utils"dist/utils/index.js and "./utils/*"assets/utils/*.