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

@tracehound/cli

v1.8.10

Published

Tracehound CLI evaluation runtime

Vulnerabilities

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

Links

Git

Maintainers

laphilosophialaphilosophia

Keywords

securityruntimecliforensicsaudit

Readme

@tracehound/cli

CLI and TUI tools for inspecting a running Tracehound runtime.

Installation

pnpm add -g @tracehound/cli
# or
npm install -g @tracehound/cli

Local usage:

pnpm dlx @tracehound/cli --help

Commands

tracehound status [--json]
tracehound stats [--json] [--since <duration>]
tracehound inspect [trace-id] [--trace-id <id>] [--signature <sig>] [--limit <n>] [--json]
tracehound watch [--refresh <ms>]
tracehound history clear [--json]
tracehound disk clear [--json]

Snapshot-backed Commands

status, stats, and watch read signed runtime snapshots written by @tracehound/core.

Required environment variables:

  • TRACEHOUND_SYSTEM_SNAPSHOT_PATH
  • TRACEHOUND_SNAPSHOT_SECRET

Optional validation overrides:

  • TRACEHOUND_SNAPSHOT_MAX_AGE_MS (default 5000)
  • TRACEHOUND_SNAPSHOT_MAX_FUTURE_SKEW_MS (default 5000)

Snapshot truth semantics:

  • stale or missing snapshot => NO_INSTANCE
  • bad signature or future-skew violation => INTEGRITY_VIOLATION

Example:

export TRACEHOUND_SYSTEM_SNAPSHOT_PATH=/var/run/tracehound/system-snapshot.json
export TRACEHOUND_SNAPSHOT_SECRET=replace-me
tracehound status

Inspect and Trace Registry Workflow

inspect, history clear, and disk clear operate on the local trace registry.

Optional environment variable:

  • TRACEHOUND_TRACE_REGISTRY_PATH to override the default trace-registry location used by inspect/history/disk commands

Typical flow:

  1. Enable emitTraceIdHeader: true in Express/Fastify adapter.
  2. Capture x-tracehound-trace-id from a quarantined response.
  3. Run tracehound inspect --trace-id <id>.

Lifecycle commands:

  • tracehound history clear clears logical inspection history while preserving the registry file path
  • tracehound disk clear removes persisted local trace-registry data from disk
  • tracehound inspect returns trace-registry metadata only; forensic payload bytes remain quarantine-local and are never exposed by the CLI

Output Modes

  • Human-readable table output by default
  • --json for machine-readable pipelines

Related Packages

Further Reading

License

Apache-2.0