← Home

@stroncium/procfs

npm Repository Homepage

Zero dependency library for reading and parsing various files from `procfs` for Node.js, implemented in pure JS.

12
Versions
CC0-1.0
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

stroncium

Keywords

procprocfsprocessuptimestatstatmstatusmountinfocpuinfoloadavgmeminfodiskstatsiodevicesfilesystemspartitionsswapsautogroupcgroupscmdlinecommcpusetcwdenvironexefdgid_maplimitsoom_scorepersonalitysetgroupstimerslack_nsuid_mapcmdlineconfigversionnodejslinux

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require loads from a fixed local subdirectory (./parsers/) using a controlled name variable from a known set — not user-controlled input. This is a safe lazy-loading pattern for this package. ai
provenance no-provenance AI (provenance): Package predates widespread Sigstore provenance adoption (2486 days old); absence of provenance is expected and not a risk signal for this package. ai

Versions (showing 12 of 12)

Version Deps Published
1.2.1 0 / 6
1.2.0 0 / 6
1.1.1 0 / 6
1.1.0 0 / 6
1.0.0 0 / 6
0.4.0 0 / 6
0.3.0 0 / 6
0.2.2 0 / 6
0.2.1 0 / 5
0.1.2 0 / 3
0.1.1 0 / 3
0.1.0 0 / 3

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
INFO No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
INFO No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
INFO No provenance attestation provenance

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

v0.1.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.