Repo brief: infinilabs/analysis-ik

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T07:12:05.278Z · commit 6d2d70fd1a23

Verdict

Healthy — Strong maintenance signals

• Last commit 2mo ago
• 28+ active contributors
• Apache-2.0 licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

analysis-ik is an Elasticsearch and OpenSearch plugin that integrates the Lucene IK analyzer for Chinese language tokenization and word segmentation. It provides two analysis modes—ik_smart (faster, fewer tokens) and ik_max_word (comprehensive, more tokens)—and supports customized dictionary configuration through XML-based settings and word lists in config/. Two-module Maven structure: core/ (ik-core) contains the Java analyzer logic (Dictionary, Lexeme, Segmenter classes under org.wltea.analyzer) and configuration; elasticsearch/ wraps it as an ES plugin with assembly configuration. Dictionary data and stopwords are in config/ as flat .dic files, loaded at runtime.

Start here

Open these first:

• core/src/main/java/org/wltea/analyzer/lucene/IKAnalyzer.java — Main Lucene analyzer entry point; defines the core tokenization pipeline and analysis chain.
• core/src/main/java/org/wltea/analyzer/dic/Dictionary.java — Dictionary management and lookup; loads and maintains all segmentation dictionaries from config files.
• core/src/main/java/org/wltea/analyzer/core/IKSegmenter.java — Core segmentation engine; performs Chinese word segmentation using maximum-matching algorithm.
• elasticsearch/src/main/java/com/infinilabs/ik/elasticsearch/AnalysisIkPlugin.java — Elasticsearch plugin integration point; registers IK analyzer and tokenizer with Elasticsearch.
• opensearch/src/main/java/com/infinilabs/ik/opensearch/AnalysisIkPlugin.java — OpenSearch plugin integration point; mirrors Elasticsearch plugin for OpenSearch compatibility.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

No setup instructions can be reliably derived from the provided data. To build locally: verify pom.xml files reference Maven; run 'mvn clean package' in the root and core/ directories. Consult the actual repository for…

Daily commands:

No executable binary or runnable demo is evident in the file list. This is a library/plugin, not a standalone service. Deployment is via Elasticsearch/OpenSearch plugin CLI: `bin/elasticsearch-plugin install https://get…

…shortened for this brief.

Key cautions & unknowns

• Concentrated ownership — top contributor handles 61% of recent commits
• Scorecard: default branch unprotected (0/10)
• Java 17 is required (maven.compiler.target=17 in core/pom.xml); older JDKs will fail builds. Dictionary files (config/*.dic) must be UTF-8 encoded and path-referenced in IKAnalyzer.cfg.xml; misconfiguration silently…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.