← Home

systeminformation

npm Repository Homepage
7
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

plusinnovations

Keywords

system informationsysinfomonitormonitoringoslinuxosxwindowsfreebsdopenbsdnetbsdcpucpuloadphysical coreslogical coresprocessorcoresthreadssocket typememoryfile systemfsstatsdiskioblock devicesnetstatsnetworknetwork interfacesnetwork connectionsnetwork statsifaceprinterprocessesusersinternetbatterydockerdocker statsdocker processesgraphicsgraphic cardgraphic controllergpudisplaysmartdisk layoutusbaudiobluetoothwifiwifinetworksvirtual boxvirtualboxvmbackendhardwareBIOSchassis

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): systeminformation legitimately uses child_process extensively to query OS/hardware info across all platforms — this is core to the library's purpose and not a security concern in itself. ai

Versions (showing 7 of 7)

Version Deps Published
5.31.7 0 / 0
5.31.6 0 / 0
5.31.4 0 / 0
5.31.3 0 / 0
5.31.2 0 / 0
5.31.1 0 / 0
5.31.0 0 / 0

v5.31.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.31.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.31.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.31.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.31.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.31.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.31.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.