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

@lssm/bundle.osint

v2.0.2

Published

Composable OSINT provider routing and operator view models

Downloads

75

Readme

@lssm/bundle.osint

Reusable composition for all supported web-access providers and OSINT operator view models. Explicit provider plans can use Serper search, Linkup or Tavily deep research, Bright Data or Massive collection/proxy methods, and Browserbase rendered sessions. API, SDK, MCP, webhook, WebSocket/SSE, browser, and proxy capabilities remain visible in provenance rather than being flattened away. Each router is pinned to one deployment, credential namespace, and provider allowlist; bounded requests persist evidence before distinct-provider corroboration. Reusable controllers, hooks, and responsive design-system screens cover loading, empty, ready, degraded, unauthorized, conflict, stale, review, and evidence states.

Operator command center

normalizeOsintCommandCenterResultV1 projects untrusted service responses into deduplicated, redacted records. It exposes only operational metadata needed for source health, acquisition, evidence, freshness, recovery, and review; unknown fields such as credentials, tokens, cookies, and personal payloads never enter the view model. Partial-provider health remains an explicit presentation state.

Mutations are rendered only from a server-returned action descriptor containing an exact operation, immutable input, authorization reference, and idempotency key. The reusable coordinator enforces an optional exact confirmation phrase and coalesces concurrent invocations with the same idempotency key. The host may further narrow operations for a route, but it never constructs an action or decides whether an effect is allowed.