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

native-machine-id

v0.2.3

Published

Native retrieval of a unique desktop machine ID without admin privileges or child processes. Faster and more reliable alternative to node-machine-id.

Readme

native-machine-id

Native retrieval of a unique desktop machine ID without admin privileges or child processes. Faster and more reliable alternative to node-machine-id.

Installation

npm install native-machine-id

Or use it directly in the CLI

npx native-machine-id
npx native-machine-id --raw

Usage

As a module

import { getMachineId } from 'native-machine-id';

// Get the machine ID, hashed with SHA-256
const hashedId = getMachineId();
console.log('Hashed Machine ID:', hashedId);

// Get the raw machine ID (should not be exposed in untrusted environments)
const rawId = getMachineId({ raw: true });
console.log('Original Machine ID:', rawId);

// Or synchronously
import { getMachineIdSync } from 'native-machine-id';
const id = getMachineIdSync();

Supported Platforms

  • macOS: Uses the IOPlatformUUID from the IOKit framework.
  • Linux: Uses the /var/lib/dbus/machine-id file to retrieve the machine ID. If this file does not exist, it falls back to /etc/machine-id.
  • Windows: Uses the MachineGuid from the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography registry.

Comparison with node-machine-id

This module provides similar functionality to node-machine-id while using native access to system APIs without the need for child processes, making it much faster and reliable.

Here's a table of performance comparisons between the two libraries, based on the average runtime from 1000 iterations of the getMachineIdSync and machineIdSync functions, from scripts/benchmark.ts:

| Test | node-machine-id | native-machine-id | Improvement | | ----------- | --------------- | ----------------- | ----------- | | Mac | | Raw | 10.71ms | 0.0072ms | 1494x | | Hashed | 12.42ms | 0.0176ms | 707x | | Linux | | Raw | 3.26ms | 0.0059ms | 557x | | Hashed | 3.25ms | 0.0088ms | 368x | | Windows | | Raw | 45.36ms* | 0.0122ms | 3704x | | Hashed | 28.66ms* | 0.0272ms | 1053x |

* - Windows tests may be inaccurate due to potential caching.

Migrating from node-machine-id

If you were previously using node-machine-id, you can use the following mapping to get a result with the following hashing transformation. This is not guaranteed always to 1:1 match the output of node-machine-id for all cases. For example on Linux, it falls back to /etc/machine-id if /var/lib/dbus/machine-id is not available.

import { createHash } from 'crypto';
import { getMachineIdSync } from 'native-machine-id';

function machineIdSync(original: boolean): string | undefined {
  const rawMachineId = getMachineIdSync({ raw: true }).toLowerCase();

  return original
    ? rawMachineId
    : createHash('sha256').update(rawMachineId).digest('hex');
}

Credits

Influenced by the work from denisbrodbeck/machineid and automation-stack/node-machine-id.

License

Apache-2.0