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

signalk-history-explorer

v0.2.12

Published

Webapp to explore Signal K History API data

Readme

Signal K History Explorer

Signal K webapp for exploring paths recorded by a History API provider over a selected time range.

Install

Install signalk-history-explorer in Signal K. It enables itself when the server restarts after installation, unless you have explicitly disabled it. Then open History Explorer from the Webapps menu. The explorer uses the local Signal K server. Choose a context (boat) or ALL, a start and end date, filter the available paths, then expand a path to read its values. ALL queries each context for the opened path and merges the results by timestamp. Every value displays its context and source when available.

The plugin uses the History API v2 endpoints, so it requires an active history provider such as signalk-to-influxdb2, signalk-parquet, or signalk-questdb.

MVP scope

  • start and end date selection;
  • context (boat) selection from the History API, including ALL;
  • the effective History API provider identifier in the period bar;
  • path filtering and collapsible path groups;
  • lazy loading: path values are requested only when a path is expanded;
  • numeric chart and chronological value table;
  • chronological text and state values;
  • context and source columns on every value; source and unit are shown when supplied by the History API.

The History API currently lists paths for the whole period rather than filtering them by context. A path can therefore appear for a boat that has no values for it. Source attribution depends on the provider; a dash is shown when it is unavailable.