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

darknode

v0.0.0

Published

HTTP/Docker interface for Darkweb/yolo

Downloads

6

Readme

darknode

A micro HTTP service that runs darknet / yolo on provided images/video's. This allows you to easily offload this heavy computing to a cloud server that has support for GPU.

Table of Contents

Installation

The package is published to npm and can be installed by running:

npm install --save darknode

Configuration

{
  //
  // Port number the HTTP server should listen on.
  //
  "port": 8080,

  //
  // Sets a pre-configured log level as for development we want to be more
  // verbose.
  //
  "NODE_ENV": 'development',

  //
  // Basic Auth configuration. Every server is configured with basic auth by
  // default. User and pass must match this value in order to be processed.
  //
  "name": "secret-username",
  "password": "secret-password",

  //
  // Timeout, how long do we allow the darknet process to run before we consider
  // it's computation to long and in need of killing. Can be a human readable
  // string or a number.
  //
  "timeout": "20 minutes",

  //
  // How many times should we retry in case of failure.
  //
  "retries": 3,

  //
  // Amount of process we're allowed to run concurrently so we don't accidentally
  // fork bomb our selfs
  //
  "concurrency": 10,

  //
  // Duration of how long we should leave the files we download and process
  // around. Ideally we want our server / image to stay as clean as possible.
  //
  "expiree": "30 minutes"
}

API Client

The library ships a Node.js Client that can be used to interact with the created server.

const DarkNode = require('darknode/client');

const api = new DarkNode({
  username: 'matching username of what is specified in config',
  password: 'matching password of what is specified in config',
  api: 'http://address-of-server.here/'
})

The client expects 3 options:

  • username The basic auth username that you configured on teh server.
  • password The password for the basic auth username.
  • api The actual address of your DarkNode HTTP server.

There are 2 different ways to receive the data from the DarkNode server, but they both assume the same options as arguments:

  • payload URL of where the asset is hosted, and requires detection.
  • record Record the DarkNode detection.
  • bgr24 Use bgr24 instead of rgb24 for color encoding.

stream

Asks the server to respond with an EventSource / ServerSentEvent response which will receive the detections of your uploaded asset in near real-time.

const stream = client.stream({
  payload: 'https://aws.cloud.server/video.mp4'
});

stream.on('data', (detection) => {
  console.log('detection')
});

fetch

Waits until the all the detections is done to return the response from the server.

client.fetch({
  payload: 'https://aws.cloud.server/video.mp4'
}, function (err, payload) {
  if (err) throw err;

  console.log(payload); // Array with all detections
});