tensorflow/tfjs

A WebGL accelerated JavaScript library for training and deploying ML models.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 56 minutes ago
Added to GitGenius on September 3rd, 2026
Created on March 5th, 2018
Open Issues & Pull Requests: 382 (+0)
GitHub issues: Enabled
Number of forks: 2,030
Total Stargazers: 19,138 (+0)
Total Subscribers: 316 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

TensorFlow.js is a hardware-accelerated JavaScript library for training and deploying machine learning models in the browser and Node.js.

The library addresses the need to run machine learning workloads on client-side JavaScript environments without requiring a separate backend server. It provides multiple APIs at different abstraction levels: a low-level Core API for numerical computation and neural networks, a high-level Layers API modeled after Keras, and specialized APIs for data loading, model conversion, visualization, and AutoML. The tool supports multiple execution backends including WebGL for GPU acceleration in browsers, WebAssembly for broader compatibility, a CPU backend for Node.js, and WebGPU for newer platforms. This allows developers to choose the right performance and compatibility tradeoff for their deployment target.

Adoption makes sense for projects that need to run inference or training directly in web browsers or Node.js environments, particularly when leveraging client-side data or sensor inputs. The library is well-suited for applications requiring real-time predictions without server round-trips, browser-based model retraining, or running existing TensorFlow models converted to the JavaScript format. The modular package structure lets you import only the components you need if bundle size is a concern.

The project maintains active engagement with a substantial user base, as evidenced by the fact that nearly all open issues originate from external users rather than the core team. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker centers on bug fixes, requests for additional information from reporters, and contributions welcomed from the community.