cpu-features
A simple binding to Google's cpu_features library for obtaining information about installed CPU(s)
cpu-features@0.0.10 was published on 2024-05-03. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=10.0.0.
All cpu-features versions · Permanent reference to 0.0.10
Package specifications
| Version | 0.0.10 |
|---|---|
| License declaration | Not declared |
| Published | 2024-05-03T04:57:36.042Z |
| Node.js requirement | >=10.0.0 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 562.52 KiB |
| Published file count | 144 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./lib/index |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 2 |
| Repository stars | 50 |
| Repository forks | 21 |
Install cpu-features 0.0.10
npm install cpu-features@0.0.10 pnpm add cpu-features@0.0.10 yarn add cpu-features@0.0.10
Runtime dependencies
- buildcheck ~0.0.6
- nan ^2.19.0
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- buildcheck@0.0.7 — direct
- nan@2.30.0 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Code-Review | 0/10 — Found 0/30 approved changesets -- score normalized to 0 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| SAST | 0/10 — no SAST tool detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Signed-Releases | 0/10 — Project has not signed or included provenance with any releases. |
| Security-Policy | 0/10 — security policy file not detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/cpu-features/0.0.10 — retrieved 2026-10-29T14:54:01.419Z
- https://api.deps.dev/v3/systems/npm/packages/cpu-features/versions/0.0.10:dependencies — retrieved 2026-10-29T14:54:02.040Z
- https://api.deps.dev/v3/systems/npm/packages/cpu-features/versions/0.0.10 — retrieved 2026-10-29T14:54:02.041Z
- https://api.deps.dev/v3/projects/github.com%2Fmscdex%2Fcpu-features — retrieved 2026-10-29T14:54:02.178Z