Automic VaultAutomic Vault

brew

使用 Homebrew, MacPorts 安装 cabocha

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

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install cabocha

local Homebrew formula metadata

MacPorts已验证 · 94%
sudo port install cabocha

MacPorts ports tree · textproc/cabocha/Portfile · 来源: api.github.com

概览

软件包摘要

Yet Another Japanese Dependency Structure Analyzer

命令和别名

  • cabocha
  • cabocha-config

历史

项目历史与用法

CaboCha is Taku Kudo's Japanese dependency structure analyzer. It is a classic Japanese NLP command-line tool built around chunking and dependency parsing, with MeCab and CRF++ as important parts of its toolchain.

项目历史

The official CaboCha page describes it as a Japanese dependency parser based on Support Vector Machines. Its cited research lineage includes the 2002 paper on Japanese dependency analysis using cascaded chunking by Taku Kudo and Yuji Matsumoto.

CaboCha offered more than a single CLI: the project page lists flexible input formats, user-redefinable features for dependency identification, user-trainable models, a Double-Array trie inside its dictionary machinery, named-entity analysis based on the IREX definition, and C, C++, Perl, and Ruby libraries.

The package sits in Taku Kudo's broader Japanese NLP tooling family. The install docs require MeCab and a dictionary such as mecab-ipadic, mecab-jumandic, or UniDic, and they require CRF++ 0.55 or later.

采用历史

CaboCha was widely known in Japanese NLP and corpus-processing workflows because it paired a scriptable CLI with trained models and published parser output formats. The official page's license notes explain that bundled model files were trained from Mainichi Newspaper CD-ROM data and carried separate usage constraints, while users could train their own models for other use cases.

In package-manager culture, CaboCha is the kind of older research-to-tooling artifact that survives because it remains useful for Japanese text-processing pipelines and because it integrates with MeCab, one of the best-known Japanese morphological analyzers.

使用方式

Users run cabocha on Japanese text from standard input and receive a simple dependency tree by default. The -f1 option emits a machine-oriented format with chunk and token information, and cabocharc controls parser, chunker, and named-entity model paths.

The install path supports Unix builds with configure, make, make check, and make install, and Windows builds that expect MeCab to be installed first. The config file can switch between IPA, JUMAN, and UniDic part-of-speech/model settings.

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

For package nerds, CaboCha is significant as a packaged research NLP tool: it wraps academic dependency parsing, model files, morphological analyzer dependencies, and C/C++ library bindings into a Unix-style command.

It also illustrates the packaging awkwardness of NLP tools with trained models: the code has an open software license, while bundled model data can carry corpus-specific redistribution and use constraints.

时间线

  • 2002: Kudo and Matsumoto published the cascaded chunking Japanese dependency analysis work cited by CaboCha.
  • 2013-12-31: CaboCha 0.67 improved analysis speed and fixed OS X and Windows issues.
  • 2014-03-10: CaboCha 0.68 removed the tournament model and added a MeCab-compatible -u option.
  • 2015-01-24: CaboCha 0.69 changed several Chunk fields to size_t and fixed a FreeList buffer overflow issue.

Related projects

  • MeCab is the morphological analyzer required by CaboCha.
  • CRF++ is required by the official CaboCha build instructions.
  • ChaSen is explicitly noted as not supported by CaboCha's install instructions.
  • JUMAN, mecab-ipadic, mecab-jumandic, and UniDic are related dictionary or part-of-speech ecosystems used around CaboCha models.

安全态势

风险级别:绿色

narrow executable package without higher-risk signals.

风险分类器

绿色 风险 · 低 置信度 · appliance

原因

  • narrow executable package without higher-risk signals

信号

  • metadata:no-higher-risk-signals

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • Homebrew bottle 元数据适用于 13 个平台目标。
  • 安装时包含 3 个运行时依赖。

建议审查

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

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
/usr/local/etc/cabocharc

可执行文件

已安装的可执行文件

命令类型暴露范围备注
cabochacli全局可执行文件
cabocha-configcli全局可执行文件

新鲜度

版本和新鲜度

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

页面生成时间2026-07-25
管理器版本0.69
管理器更新时间2026-06-30
本地数据OK
上游not checked
检测到的最新版本未检测到

https://taku910.github.io/cabocha/

安装元数据

软件包元数据

软件包键brew:cabocha
版本0.69
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/cabocha
主页https://taku910.github.io/cabocha/
上游文档https://taku910.github.io/cabocha
许可证BSD-3-Clause OR LGPL-2.1-or-later
源码归档https://distfiles.macports.org/cabocha/cabocha-0.69.tar.bz2
最后更新2026-06-30T11:34:46-04:00
Pulseupdated
依赖crf++, mecab, mecab-ipadic
Bottle可用 (于 arm64_big_sur, arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, big_sur, catalina, monterey, sonoma, ventura, x86_64_linux)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

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

源数据库匹配

其他软件包管理器记录

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

MacPorts95%

cabocha

sudo port install cabocha
  • normalized package name match
  • 匹配方式:Cabocha
MacPorts ports tree · api.github.com · MacPorts ports tree: textproc/cabocha/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

来源线索

由仓库数据生成

此页面由 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 configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment