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-engine-hours-seren

v1.7.0

Published

Persistent engine hours logger with a noise threshold. Fork of signalk-engine-hours.

Readme

signalk-engine-hours-seren

Fork of KEGustafsson/signalk-engine-hours published as signalk-engine-hours-seren.

What's different: the original counts an engine as running whenever revolutions > 0. A stopped engine's rev sensor can report small phantom values (0.03–4 rev/s were seen at anchor), and every one of those added time to runTime. On one boat that inflated four months of engine hours by 45–70%. This fork adds a runningThreshold setting (rev/s, default 5 = 300 rpm). Revolutions at or below it count as stopped. Set it to 0 for the original behaviour.

The plugin id is still signalk-engine-hours, so an existing engines.json, plugin configuration and web app carry over. Uninstall the original package before installing this one. Both packages register the same plugin id.

Signal K engine hours logger keeps engine runtime data in persistent storage. Engines that report revolutions to the Signal K server are logged automatically. Users can change how often engine revolutions are monitored; the current default is 60s. When the Signal K server starts, previously logged data is read from persistent storage. Runtime data is written to persistent storage shortly after changes (debounced). From the WebApp, engine runtimes can be set and changed.

Versions

  • v0.0.1 Initial release
  • v0.1.0 Improvements, custom API and simple hours editor
  • v0.1.1 Improvements to editor
  • v0.2.0 runTimeTrip added and improvements to editor
  • v0.2.1 fix for runTimeTrip meta
  • v0.3.0 editor UI modifications
  • v0.3.1 fixes to editor UI
  • v0.4.0 tooltip to show hrs:min
  • v1.0.0 1st release
  • v1.1.0 fix: improve error handling and validation for engine data
  • v1.2.0 feat: option to monitor propulsion.*.state
  • v1.3.0 new UI and fixes to code
  • v1.3.1 chore: clean-up
  • v1.4.0 feat: improved time calculation accuracy
  • v1.4.1 fix: engine hours accrual bug
  • v1.5.0 feat: engine hours reporing optimized
  • v1.6.0 fix: accrual clamp, auth, input hardening, UI state
  • v1.7.0 (seren fork) feat: runningThreshold — ignore sub-threshold revolutions (sensor noise from stopped engines)