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

curiosus-sdk

v0.2.3

Published

Technology detection SDK - detect any web technology from any URL

Readme

curiosus-sdk

Detect web technologies on any website. Currently supports Lenis smooth-scroll detection, with a plugin system for adding more technologies.

Install

npm install curiosus-sdk
# or
bun add curiosus-sdk

Two Modes

Lite (recommended for most use cases)

No Puppeteer. No browser. Just fetch. Works everywhere — browser, Node.js, Vercel, edge runtimes.

import { CuriosusLite } from "curiosus-sdk"

const curiosus = new CuriosusLite()
const { technologies } = await curiosus.detect("https://darkroom.engineering")

console.log(technologies)
// [{ name: "lenis", detected: true, version: null, method: "html-attributes (lite)" }]

How it works:

  1. Fetches the page HTML
  2. Checks for Lenis CSS classes and data-lenis attributes
  3. Searches inline <script> tags for Lenis markers
  4. Fetches external JS files in parallel and searches them for Lenis code + version

~2-3 seconds per site. Detects ~80% of Lenis sites.

Full (maximum accuracy)

Uses Puppeteer to launch a real browser. Executes JavaScript, triggers scroll events, waits for hydration — catches everything.

import { Curiosus } from "curiosus-sdk"

const curiosus = new Curiosus()
const { technologies } = await curiosus.detect("https://darkroom.engineering")

console.log(technologies)
// [{ name: "lenis", detected: true, version: "1.3.17", method: "window.lenisVersion" }]

How it works:

  1. Launches headless Chromium
  2. Navigates to the URL (3-tier fallback: networkidle2 > domcontentloaded > partial load)
  3. Scrolls through the page to trigger lazy-loaded scripts
  4. Dispatches scroll, wheel, and touch events to trigger library initialization
  5. Waits for React/Next.js hydration
  6. Runs 5 detection methods:
    • window.lenisVersion global (source of truth)
    • window.Lenis constructor check
    • window.lenis instance check
    • HTML element attributes (class="lenis", data-lenis)
    • Bundled script proximity search for version strings

~5-11 seconds per site. Requires Node.js.

Fast mode

Cuts wait times in half for interactive use:

const curiosus = new Curiosus({ fast: true })
const { technologies } = await curiosus.detect("https://darkroom.engineering")
// Same accuracy, ~5s instead of ~11s

Multiple URLs

Both modes support batch detection:

// Lite — runs all in parallel
const curiosus = new CuriosusLite()
const results = await curiosus.detectMany([
  "https://darkroom.engineering",
  "https://linear.app",
  "https://google.com",
])

// Full — sequential with browser lifecycle management
const curiosus = new Curiosus()
const results = await curiosus.detectMany([
  "https://darkroom.engineering",
  "https://linear.app",
])

Which Mode Should I Use?

| Scenario | Mode | |----------|------| | Frontend / browser app | Lite | | Vercel / serverless | Lite | | Quick check from a script | Lite | | CI pipeline | Lite | | Need version detection | Full | | Need maximum accuracy | Full | | Batch analysis (hundreds of sites) | Full | | Sites with lazy-loaded Lenis | Full |

Configuration (Full mode)

const curiosus = new Curiosus({
  // Reduce wait times for faster results (default: false)
  fast: true,

  // Per-site timeout in ms (default: 60000)
  timeout: 30_000,

  // Custom Chromium path (e.g., for Railway, Docker)
  executablePath: "/usr/bin/chromium",

  // Domains to skip
  blacklistedDomains: ["example.com"],

  // Custom logger
  logger: {
    log: (msg) => console.log(msg),
    warn: (msg) => console.warn(msg),
    error: (msg) => console.error(msg),
  },
})

Custom Detectors (Full mode)

Add your own technology detectors using the plugin interface:

import { Curiosus, type Detector, type TechnologyResult } from "curiosus-sdk"
import type { Page } from "puppeteer"

class GsapDetector implements Detector {
  name = "gsap"

  async detect(page: Page): Promise<TechnologyResult> {
    const result = await page.evaluate(() => {
      const w = window as unknown as Record<string, unknown>
      const hasGsap = typeof w.gsap === "object" && w.gsap !== null
      const version = hasGsap ? String((w.gsap as Record<string, unknown>).version || "") : null
      return { hasGsap, version }
    })

    return {
      name: this.name,
      detected: result.hasGsap,
      version: result.version,
      method: result.hasGsap ? "window.gsap" : null,
    }
  }
}

const curiosus = new Curiosus()
curiosus.use(new GsapDetector())

const { technologies } = await curiosus.detect("https://some-site.com")
// [
//   { name: "lenis", detected: true, version: "1.3.17", ... },
//   { name: "gsap", detected: true, version: "3.12.5", ... }
// ]

Response Shape

Both modes return the same structure:

interface DetectionResult {
  url: string
  technologies: TechnologyResult[]
}

interface TechnologyResult {
  name: string          // "lenis"
  detected: boolean     // true/false
  version: string | null // "1.3.17" or null
  method: string | null  // detection method that matched
}

License

MIT