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 🙏

© 2025 – Pkg Stats / Ryan Hefner

work-hive

v0.0.1

Published

A lightweight, browser-based, grid computing platform built for NodeJS.

Vulnerabilities

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

Links

Git

Maintainers

jimbuckjimbuck

Keywords

griddistributedclustergrid computingdistributed computingcluster computinghiveworkersolve

Readme

WorkHive (formerly Node@home)

Why a rename? Because after 2+ years of not touching this project, I finally have time and motivation to work on it! Fresh ideas need fresh names, so while the repository is the same, the direction I want to take it is different. The codebase is squeeky clean and ready for a much simpler approach.

This is a standalone server for creating, managing and serving work items for grid-based computational networks. Grid computing allows for client browsers to run calculations and send the result back to your server. This standalone server handles all of the heavy lifting that is required to manage data, requests, and queueing.

While Javascript does not have the highest raw performance, the sheer number of devices that natively run it in the browser is overwhelming. My end goal is to discover the power of distributed javascript computing. If we can harness javascript on enough devices, the computational power may be sufficient to solve complex problems in sufficient time frames.

What can I use it for?

  • Rendering and Image Processing (Render farm, image recognition, etc.)
  • Mathematical Theories and Calculations (Collatz Conjecture, N Queens, etc.)
  • Statistical Simulations and Experiments (Artificial Life, Physics Simulations, etc.)
  • Anything you can write in javascript! (Hopefully for the betterment of humanity...)

How does it work?

WorkHive is composed of three components:

  1. Server
  • [ ] Built with ExpressJS and NeDB.
  • [ ] Serves client scripts.
  • [ ] Manages work items in the queue.
  • [ ] Sends work parameters and records completed results.
  1. Workers
  • [ ] Executes compute functions against work parameters.
  • [ ] Utilizes webworkers when possible.
  • [ ] Sends results back to server.
  1. Admin
  • [ ] Simple web portal.
  • [ ] View live stats.
  • [ ] Edit the compute functions
  • [ ] Manage work item queue.
  • [ ] Disconnect workers.
  • [ ] Export results to various datatypes.

How safe/reliable is it?

Security is at the utmost importance when designing a grid computation platform. Standard defenses will be in place to protect the project against rogue data. Depending on the problem, solutions will be verified through repetition or via a validate function if supplied. In the mean time, be sure to use SSL, and require multiple trials before accepting the result.