@tensorflow/tfjs-backend-cpu 3.17.0

Vanilla JavaScript backend for TensorFlow.js

@tensorflow/tfjs-backend-cpu@3.17.0 was published on 2022-05-12. Its manifest declares 2 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @tensorflow/tfjs-backend-cpu versions · Permanent reference to 3.17.0 · Latest release

Package specifications

Version3.17.0
License declarationApache-2.0
Published2022-05-12T23:17:07.973Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size9245.68 KiB
Published file count424
Package typeNot declared
ES module entrydist/index.js
Default entrydist/tf-backend-cpu.node.js
Side effects declaration["./dist/register_all_kernels.js","./dist/base.js","./dist/index.js","./src/register_all_kernels.mjs","./src/base.mjs","./src/index.mjs"]
Direct advisories0
Resolved graph dependencies2
Repository stars19151
Repository forks2028

Install @tensorflow/tfjs-backend-cpu 3.17.0

npm install @tensorflow/tfjs-backend-cpu@3.17.0
pnpm add @tensorflow/tfjs-backend-cpu@3.17.0
yarn add @tensorflow/tfjs-backend-cpu@3.17.0

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

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.

Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Code-Review9/10 — Found 29/30 approved changesets -- score normalized to 9
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
License10/10 — license file detected
Binary-Artifacts9/10 — binaries present in source code
Security-Policy0/10 — security policy file not detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Fuzzing0/10 — project is not fuzzed

Evidence and freshness