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

@inspecto-dev/core

v0.3.16

Published

Core browser runtime and server logic for Inspecto

Downloads

896

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

hugo.felixhugo.felix

Keywords

aidevtoolsinspectorcore

Readme

@inspecto-dev/core

@inspecto-dev/core is the browser runtime for Inspecto.

Overview

This package focuses on the browser-side runtime:

  1. Browser Client: A native Web Component (<inspecto-overlay>) utilizing Shadow DOM for style isolation. It captures DOM clicks, parses the injected source location attributes (data-inspecto), and provides the interactive UI menu.
  2. Prompt Assembly: Builds inspect and annotate payloads in the browser, including optional runtime, CSS, and snippet context.
  3. Workflow Dispatch: Renders configured workflow buttons from prompts.json and sends project-level instructions such as deploy or PR review to the configured agent route.
  4. Agent Session Visibility: Renders MCP annotation and workflow session state in the browser, including queued, acknowledged, progress reply, resolved, and dismissed timeline events.

The local development server, snippet extraction, and IDE dispatch runtime live in @inspecto-dev/plugin.

Core Implementation

  • Web Component: Implemented with pure native DOM APIs and goober for CSS-in-JS inside the Shadow DOM, ensuring zero framework dependency and avoiding conflicts with user styles.
  • Intent System: Defines the default AI actions (Explain, Fix Bug, Code Review, etc.) and handles prompting.
  • Context Assembly: Requests optional snippet/runtime/CSS context and appends it to the outgoing prompt.
  • Workflow Buttons: Displays project-specific workflow entries such as Deploy Preview or Review & PR, letting agents execute them with their own skills, MCP servers, and tools.
  • Session Timeline: Converts annotation and workflow sessions into deterministic timeline items and renders the latest agent task progress in Annotate mode.
  • Overlay Runtime: Mounts and configures the browser overlay via mountInspector() / unmountInspector().

Modes

  • Inspect mode: single-target inspect and immediate actions.
  • Annotate mode: multi-target annotation, sidebar queueing, structured AI task dispatch, custom workflow buttons, and MCP session progress visibility.

Use inspect when you want to act on one element immediately. Use annotate when one problem spans multiple linked components, or when you want to hand off a durable task or custom workflow to an agent and monitor its progress from the browser.