Library / SDK
sebhildebrandt/systeminformation avatar
sebhildebrandt/systeminformation

systeminformation: three linters, a CommonJS manifest, and a beta branch

System Information Library for Node.JS

3,144 stars350 forksJavaScriptMIT

At a glance

What is it?
systeminformation is a dependency-free Node.js library for hardware and OS facts that states outright it will not run in a browser. The repository carries three linter configs, a version 6 TypeScript beta living on its own branch, and a documented install line whose save flag is written with the wrong character.
Who is it for?
systeminformation fits a server process that needs to report on its own machine across many operating systems without pulling in a dependency tree, and it does not fit anything running in a page, because the file says so outright. Verify four things first.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 4 days ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 22, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • sebhildebrandt/systeminformation3,144 ★ · +7
Star history
Repository2026-09-242026-11-22
sebhildebrandt/systeminformation3.1k3.1k

7 Stars in the last 59 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The library states it will not work in a browser

One sentence in the runtime section is worth more than any feature list, and it carries an attention marker: the library is supposed to be used as a backend or server-side library and will definitely not work within a browser. That constraint explains a good deal of the design. It is why the package declares no npm dependencies, since it reaches into the operating system directly rather than wrapping a library. It is why the manifest sets the module type to commonjs and points the entry point at a plain JavaScript file in `lib/`. And it is why the interesting capability is breadth: more than 50 functions across the system, CPU, baseboard, battery, memory, disks and filesystem, network, Docker, software, services and processes. The command line version of the same idea is a single bare call, where the second form may take up to 30 seconds:

code
# get basic system info (System, OS, CPU)
npx systeminformation info

# obtain all static data - may take up to 30 seconds
npx systeminformation

Everything either form reports is read from the machine it is running on, which is exactly the set of things a browser will not let a page ask for.

The version 4 install line carries a long dash where the save flag belongs

Four install commands are documented, and one of them cannot work. For the current version there are two equivalent forms, `npm install systeminformation --save` and the shorter `npm i systeminformation`. For version 4 there are two more, and the first writes the save flag with a single long dash between the version specifier and the word save, where two ordinary hyphens belong. Copying that line verbatim into a shell produces an argument npm will not recognise as a flag. The line immediately below it, `npm install systeminformation@4`, is correct, so the fix is present in the same section. This is the kind of defect that survives in a file read by thousands of people, and it is only findable by copying the command rather than reading about it.

A caretaking badge on a project the README says started for himself

The badge row carries seven items: an npm version badge, an npm downloads badge, git issue and closed issue counts, a sponsoring badge, a badge labelled caretaker, and the MIT licence badge. A caretaker badge is a succession marker, and it sits on a repository whose own front page says the project started as a small project just for myself. The rest of the file is written the same way. The support section states that more than 3.000 hours were spent working on it and that money was invested in hardware so it could be tested on different platforms, and the funding link is a Buy me a coffee page. The number is also written with a period as the thousands separator, a European convention sitting in an otherwise American-English document.

The project section opens with This is amazing and then five adoption numbers

The section introducing the project begins with the sentence This is amazing. The rest of the paragraph is five figures: more than 20,000 lines of code, more than 750 versions published, up to 50 million downloads per month, more than 700 million downloads overall, and a claim of a top 5 ranking among npm backend packages. Every one of them is self-reported, none is dated, and none links to anything a reader could check, such as an npm page or a download chart. The count of published versions is the one that can be reasoned about from the repository itself: with the current line in the 5.33 range and a 7.10 tag still visible in the release list, the total is plausible but unverifiable from what is written here. What is verifiable is that the superlative and the numbers sit in the same paragraph, so a reader has to take both on trust.

Version 6 lives on a branch, and a beta tag landed seven minutes after a stable one

The two newest releases were published on the same afternoon, v5.33.15 at 16:40 and v6.0.0-beta.17 at 16:48 on 2026-09-30. The default branch is master, and version 6 is not there: the local test instructions tell you to clone a branch named `v6` and work through this sequence.

bash
# clone v6 branch
git clone -b v6 https://github.com/sebhildebrandt/systeminformation.git
cd systeminformation

# install dev dependencies and build
npm ci
npm run build

# run tests
npm run ci      # for the whole test run
npm run test    # for testing individual functions

Beta seventeen also sits against a report instruction that is one release out of date, asking for issues to be prefixed with a string reading v6.beta.0. The changelog section in the same file is headed as the last seven major and minor releases and then lists ten, from 5.33.0 down to 5.24.0, and its last visible line is an incomplete fragment. So the release tracking inside the front page is approximate in three separate ways.

The v6 instructions ask for two npm scripts this manifest does not have

Read the version 6 test recipe against the manifest. The recipe asks for `npm run build` and `npm run ci`. The scripts the manifest defines are three: `test` running a Node file under the test directory, `testDeno` running the same file through Deno with the `-A` flag, and `testAll` running a different file the same way. Neither requested script name is among them. The manifest reads version 5.33.15, which is the master line, so some of the gap is expected, and the version 6 branch presumably carries its own manifest. It is still worth knowing that the published recipe and the published script list do not line up. The Deno entry is also the one place where a runtime grants itself blanket permissions rather than a scoped list, on a library whose entire job is reading the machine it runs on.

Three linters, one of them deprecated, and CommonJS for a TypeScript rewrite

The root carries `.eslintrc`, `tslint.json` and `biome.json`, plus an `.editorconfig`. Three separate lint and format configurations for one package is one too many, and the choice of TSLint is the tell: it was written for TypeScript projects and then deprecated in favour of using ESLint instead, so the repository configures the successor and the predecessor at once, with Biome overlapping the formatting role of both. The same pattern shows up in the build story. Version 6 is described as written completely in TypeScript, and the manifest already points a types field at a declaration file inside `lib/`, yet the module type stays commonjs and no TypeScript configuration file appears at the top level.

Windows is called partial support while Windows keeps getting features

The platform line names Linux, macOS, partial Windows, FreeBSD, OpenBSD, NetBSD, SunOS and Android, with the word support appearing twice in one sentence. The hedge lands on Windows, and it sits awkwardly beside the release notes, which record Windows-specific additions in three consecutive entries: a user field added to the processes function in 5.30.0, and an operating system code name added to osInfo in 5.29.0. The manifest also begins an operating system allowlist whose first entry is darwin, and the file ends there, inside an unterminated string, so the rest of the allowlist is not visible. Version 5 did widen the hardware side, adding audio, bluetooth, printer and USB functions and Apple Silicon support from M1 through M5.

Editorial conclusion

systeminformation fits a server process that needs to report on its own machine across many operating systems without pulling in a dependency tree, and it does not fit anything running in a page, because the file says so outright. Verify four things first. Decide which major version you are on, because version 6 is still a beta with breaking API changes and lives on a separate branch from the one you get by default. Decide how you will install it, because one of the four documented install lines is broken by a single character. Read the platform scope before committing, since Windows is described as partial support even though Windows-specific additions keep landing. And run the tests with care, since the Deno script runs with an unrestricted permission flag on a library that only ever wants machine-wide access.

Frequently asked questions

What is sebhildebrandt/systeminformation?

A Node.js library described as a lightweight collection of more than 50 functions for retrieving hardware, system and operating system information, with no npm dependencies. It covers the system, CPU, baseboard, battery, memory, disks and filesystem, network, Docker, software, services and processes, and the file states it is meant for backend use and will not work inside a browser.

Which platforms does sebhildebrandt/systeminformation support?

The file names Linux, macOS, partial Windows, FreeBSD, OpenBSD, NetBSD, SunOS and Android, and separately records testing against Node.js, Bun and Deno. For Deno, one problem was recorded: an incorrect os.freemem() fill-in on versions up to 2.1.4, fixed from Deno 2.1.5 onwards.

Is there a version 6 of sebhildebrandt/systeminformation?

A version 6 beta, installed with npm i systeminformation@beta. It is described as written completely in TypeScript with the API cleaned up and breaking changes, and it lives on a separate branch called v6 rather than on the default master branch. The newest beta tag is v6.0.0-beta.17 from 2026-09-30.

Can sebhildebrandt/systeminformation run in a browser?

No. The file states under an attention marker that the library is supposed to be used as a backend or server-side library and will definitely not work within a browser, since everything it reports is read from the machine the process runs on.

How do I call sebhildebrandt/systeminformation from a command line?

The manifest declares a binary named systeminformation pointing at lib/cli.js. Calling it with the info argument returns basic information covering the system, the operating system and the CPU. Calling it with no argument obtains all static data, which the file says may take up to 30 seconds.

What do the sebhildebrandt/systeminformation test scripts run?

Three are defined: one running a Node file under the test directory, one running that same file through Deno with the -A flag instead of a scoped permission list, and one running a separate file the same way under Node. The version 6 instructions in the front page ask for npm run build and npm run ci, and neither script name appears in this manifest.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. sebhildebrandt/systeminformation on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/sebhildebrandt-systeminformation.svg)](https://hysenlabs.com/projects/sebhildebrandt-systeminformation)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/sebhildebrandt-systeminformation.svg)](https://hysenlabs.com/projects/sebhildebrandt-systeminformation)

Was this useful?