Automic VaultAutomic Vault

brew

使用 Homebrew, Nix 安装 libtensorflow

查看 libtensorflow 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install libtensorflow

local Homebrew formula metadata

概览

软件包摘要

C interface for Google's OS library for Machine Intelligence

命令和别名

  • benchmark_model
  • summarize_graph
  • transform_graph

历史

项目历史与用法

libtensorflow is the packaged C interface to TensorFlow, Google's open-source machine-learning platform. In package-manager terms it is the part of TensorFlow that lets non-Python programs bind to TensorFlow's runtime through C headers and shared libraries.

项目历史

Google announced TensorFlow as an open-source release on November 9, 2015, describing it as the second-generation machine-learning system built after DistBelief. The announcement emphasized portability, production readiness, Apache 2.0 licensing, and use across Google research and products.

The TensorFlow repository README says the framework was originally developed by researchers and engineers in the Google Brain Machine Intelligence team for machine-learning and neural-network research, while also being versatile enough for other areas. The C installation documentation defines the C API in c_api.h and says it is designed for simplicity and uniformity rather than convenience.

The libtensorflow packaging story is narrower than TensorFlow's Python ecosystem. It provides downloadable C library archives, headers, and shared libraries for supported operating systems, so language bindings and C/C++ applications can use TensorFlow without installing the full Python package path.

采用历史

TensorFlow's adoption was unusually fast for machine-learning infrastructure. Google Cloud's 2016 Jeff Dean interview said TensorFlow gained over 11,000 GitHub stars in its first week after launch, and Google's first-year post reported more than 480 direct contributors by November 2016.

By October 20, 2022, the TensorFlow team described the project as adopted by millions of developers, used across Google products, and connected to TensorFlow Lite, TensorFlow.js, Keras, OpenXLA, DTensor, and production model tooling. libtensorflow's adoption follows from that ecosystem as the C ABI surface used by bindings and native applications.

使用方式

C users install a libtensorflow archive, include tensorflow/c/c_api.h, link against the shared library, and call functions such as TF_Version. The official C page documents separate Linux, macOS, and Windows archives and notes platform-support endpoints with concrete TensorFlow release numbers.

Package managers expose libtensorflow for users who need native linkage, embedding, or language bindings rather than the normal pip install tensorflow workflow.

为什么软件包爱好者会关心

libtensorflow is interesting because it packages a massive ML system behind a C ABI. That is exactly the kind of boundary package maintainers care about: headers, shared objects, platform archives, ABI compatibility, and wrappers in other languages.

It also shows the tension between fast-moving ML stacks and traditional system packaging. TensorFlow's Python ecosystem moves quickly, while libtensorflow gives distributions and bindings a more conventional binary-library surface.

时间线

  • 2015: Google open-sources TensorFlow on November 9, 2015.
  • 2016: Google reports more than 480 direct TensorFlow contributors during the first year after open-sourcing.
  • 2017: TensorFlow 1.0 era establishes the project as a major open-source ML framework.
  • 2022: The TensorFlow team publishes a future roadmap emphasizing XLA, DTensor, applied ML tooling, and ecosystem growth.
  • 2024: TensorFlow C documentation identifies TensorFlow 2.16 as the last TensorFlow release supporting macOS x86 C packages.
  • 2025: TensorFlow C documentation identifies TensorFlow 2.18 as the last release of Linux x86, Windows x86, and Mac Arm64 libtensorflow packages.

Related projects

  • DistBelief is TensorFlow's internal predecessor. TensorFlow Lite, TensorFlow.js, TFX, Keras, OpenXLA, DTensor, and TensorFlow Serving are related ecosystem projects and deployment paths.

安全态势

风险级别:绿色

library-like package without higher-risk signals.

风险分类器

绿色 风险 · 低 置信度 · appliance

原因

  • library-like package without higher-risk signals

信号

  • metadata:library-like

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • Homebrew bottle 元数据适用于 6 个平台目标。
  • 构建元数据列出 4 个构建依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

可执行文件

已安装的可执行文件

命令类型暴露范围备注
benchmark_modelcli全局可执行文件
summarize_graphcli全局可执行文件
transform_graphcli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-07-25
管理器版本2.21.0
管理器更新时间2026-06-22
本地数据OK
上游当前
检测到的最新版本v2.21.0

https://github.com/tensorflow/tensorflow

  • OK没有生成新鲜度警告。

安装元数据

软件包元数据

软件包键brew:libtensorflow
版本2.21.0
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/libtensorflow
主页https://www.tensorflow.org/
仓库https://github.com/tensorflow/tensorflow
上游文档https://www.tensorflow.org/api_docs
许可证Apache-2.0
源码归档https://github.com/tensorflow/tensorflow/archive/refs/tags/v2.21.0.tar.gz
最后更新2026-06-22T14:05:23-07:00
Pulseupdated
构建依赖bazelisk, gnu-getopt, numpy, python@3.13
Bottle可用 (于 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namelibtensorflow
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

源数据库匹配

其他软件包管理器记录

匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。

Nix95%

libtensorflow

nix profile install nixpkgs#libtensorflow
  • normalized package name match
  • 匹配方式:Libtensorflow
nixpkgs package indexes · raw.githubusercontent.com · nixpkgs package indexes: libtensorflow from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment