snowball
Library Listed
Rust implementation of Snowball stemming algorithms for 33 languages
- Downloads
- 21,654
- Dependents
- 3
- Stars
- 891
- Forks
- 216
- Contributors
- 43
- Commits
- 2,116
- Latest release
- 0.1.0 ·
About
Snowball is a small string processing language for creating stemming algorithms for use in Information Retrieval, plus a collection of stemming algorithms implemented using it.
Snowball was originally designed and built by Martin Porter. Martin retired from development in 2014 and Snowball is now maintained as a community project. Martin originally chose the name Snowball as a tribute to SNOBOL, the excellent string handling language from the 1960s. It now also serves as a metaphor for how the project grows by gathering contributions over time.
The Snowball compiler translates a Snowball program into source code in another language - currently Ada, C, C++, C#, Dart, Go, Java, Javascript, Object Pascal, PHP, Python, Rust and Zig are supported.
This repository contains the source code for the snowball compiler and the stemming algorithms. The snowball compiler is written in ISO C - you'll need a C compiler which support C99 to build it (but the C code it generates should work with any ISO C compiler).
See https://snowballstem.org/ for more information about Snowball.
Read the full README
What is Stemming?
Stemming maps different forms of the same word to a common "stem" - for example, the English stemmer maps connection, connections, connective, connected, and connecting to connect. So a search for connected would also find documents which only have the other forms.
This stem form is often a word itself, but this is not always the case as this is not a requirement for text search systems, which are the intended field of use. We also aim to conflate words with the same meaning, rather than all words with a common linguistic root (so awe and awful don't have the same stem), and over-stemming is more problematic than under-stemming so we tend not to stem in cases that are hard to resolve. If you want to always reduce words to a root form and/or get a root form which is itself a word then Snowball's stemming algorithms likely aren't the right answer.
Building Snowball
GNU make is required to build Snowball.
The build system is currently structured as two separate stages for many of the target languages.
The first stage builds the Snowball compiler and runs it to create target
language code (and it can also run tests on each stemmer). The expectation is
that you then create "distribution" tarballs of this code with make dist
(or create one for a specific target language, e.g. with make dist_libstemmer_c for C). These tarballs are created in the dist/
subdirectory.
To actually build the libstemmer library you then unpack and build the distribution tarball, e.g. for C::
tar xf dist/libstemmer_c-3.2.0.tar.gz
cd libstemmer_c-3.2.0
make
Cross-compiling
If cross-compiling starting from the git repo, the Snowball compiler needs to be built with a native compiler then libstemmer with the cross-compiler. For example::
make CC=cc dist_libstemmer_c
tar xf dist/libstemmer_c-3.2.0.tar.gz
cd libstemmer_c-3.2.0
make CC=riscv64-unknown-linux-gnu-gcc
If you are cross-compiling to or from Microsoft Windows, you'll need to also
work around an assumption in libstemmer's Makefile which sets EXEEXT
based on the OS you are building on::
ifeq ($(OS),Windows_NT)
EXEEXT=.exe
endif
For example, if cross-compiling from Linux to Microsoft Windows, use something like this for the libstemmer build::
make CC=x86_64-w64-mingw32-gcc EXEEXT=.exe
When going the other way, you'll need to use EXEEXT=.
Compatibility
- Runs on
- GPU support unknown
What shows it
- no dependency or feature matches a backend row
- Native code
- None found
- No native code found
- Python bindings
- No Python binding crate found
- License
- BSD-3-Clause
Compare with similar projects
Order: strongest tier first, then most downloads, then name, with unmeasured values last. A library counts downloads over 30 days. An app counts binary downloads per release. An app with none counts its crate downloads over 30 days. ML Rust runs this catalogue, so its closest project always gets a row.
| Project | Downloads | Dependents | Stars | Latest release | Runs on (GPU) | Native code | License |
|---|---|---|---|---|---|---|---|
|
Rust implementation of Snowball stemming algorithms for 33 languages |
21,654 downloads over 30 days | 3 | 891 | 0.1.0 | GPU support unknown | No native code found | BSD-3-Clause |
|
tiktoken-rs Featured
Library for encoding and decoding with the tiktoken library in Rust |
3,939,182 downloads over 30 days | 449 | 410 | 0.12.1 | GPU support unknown | No native code found | MIT |
|
A rust implementation of some popular snowball stemming algorithms |
5,399,112 downloads over 30 days | 128 | 136 | 1.2.0 | GPU support unknown | No native code found | BSD-3-Clause OR MIT |
|
splintr Listed
Tokenizer for Rust and Python: pure Rust by default, with 18 bundled vocabularies and four backends covering BPE, SentencePiece and WordPiece. Its output matches Hugging Face tokenizers id for id on 14 model families, including GPT-2, Qwen, Whisper, T5 and BERT. Python bindings |
8,204 downloads over 30 days | 7 | 63 | 0.22.2 | GPU support unknown | Binds native code: pcre2-sys (feature pcre2) | MIT |
|
frostem New
Pre-built Snowball stemmers for Rust (tracks snowball main) |
504,939 downloads over 30 days | 4 | 4 | 2.20261016.1 | GPU support unknown | No native code found | BSD-3-Clause |
|
xberg New
High-performance document intelligence library for Rust. Extract text, metadata, and structured data from PDFs, Office documents, images, and 107 formats and 371 programming languages via tree-sitter code intelligence with async/sync APIs. |
26,095 downloads over 30 days | 2 | 9,565 | 1.3.10 | CUDA, Metal | Binds native code: libheif-sys, libz-sys, xberg_libwpd, xberg_tesseract, clipper-sys and 4 more. Build uses a native toolchain: cc, bindgen (feature bindings), cmake (feature build-tesseract), pkg-config (feature dynamic-linking), vcpkg (feature dynamic-linking) | MIT |
|
🦀 A Rust implementation of a RoBERTa classification model for the SNLI dataset |
Not measured | Not applicable | 13 | Not measured | Not measured | Not measured | None stated |
Why ListedNo archive, New or Featured rule places it, so it is Listed.
What it lacks for Featured
- It has 2 active dependents and 2 new dependents in 365 days. Featured needs 11 active dependents or 9 new dependents in 365 days. The repository route reads 891 stars, 216 forks and 43 contributors. It needs 4,539 stars, 434 forks and 79 contributors together.
- The check finds no release commit or manifest that ties the crate to the repository.
What else the check found
- The last activity is on 17 Oct 2026, 23 days ago. The rules expect an update within 365 days. Dormancy rule
Check notes
- release commit 219294267e4bc35e6e42c0bf36df41c7f55ecd02 is absent from the repo
Exact rules: Listed, Featured library. The check on applied thresholds version 9.
Every rule outcome, as the check records it
expected-interval: version 0.1.0 base 80, capped at 1 releases = 50, raised to the 365-day floor: E = 365 daysdormancy: last activity 2026-10-17, 23 days ago, E = 365: activefeatured: not featured: active_users 2 < 11 and new_adopters 2 < 9 and repository route stars 891 (needs 4539), forks 216 (needs 434), contributors 43 (needs 79); repository link not verifiedlisted: listed: no archive, new or featured rule applies
Measurements and sources
Each signal row shows the raw value, its source and the fetch date. The Sources list gathers every distinct source on this page. Movement needs more history.
Sources6 sources
- Description: the crates.io description
- crates.io database dump, fetched
- RustSec advisory database, fetched
- GitHub repository, fetched
- crates.io package, fetched
- GitHub contributors, fetched
Adoption2 active dependents, 2 new dependents in 365 days1 not measured
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| Active dependents | 2 | crates.io database dump | Yes | |
| New dependents (365 days) | 2 | crates.io database dump | Yes | |
| Peak active dependents | 2 | crates.io database dump | Yes | |
| Active dependents as a share of the peak | 1 | crates.io database dump | Yes | |
| Binary downloads per release | Not measured | Yes |
MaintenanceLatest human commit: 23 days ago3 not measured
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| Latest human commit | 2026-10-17 | GitHub repository | Yes | |
| Latest release | 2025-07-24 | crates.io database dump | Yes | |
| First release | 2025-07-24 | crates.io database dump | Yes | |
| Latest version | 0.1.0 | crates.io database dump | Yes | |
| Days the oldest outside issue waits for a reply | 61 | GitHub repository | Yes | |
| Maintainer replies over 365 days | 126 | GitHub repository | Yes | |
| Repository archived | false | GitHub repository | Yes | |
| Repository gone | false | GitHub repository | Yes | |
| Release commit or manifest in the repo | false | crates.io package | Yes | |
| Published docs | true | crates.io database dump | Yes | |
| Latest release fails cargo check | Not measured | Yes | ||
| Build check date | Not measured | Yes | ||
| Build check toolchain | Not measured | Yes |
SecurityUnpatched vulnerabilities: none
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| Unpatched vulnerabilities past the grace window | none | RustSec advisory database | Yes | |
| RustSec unmaintained advisory | none | RustSec advisory database | Yes | |
| Deprecation notice | none | crates.io database dump | Yes | |
| Deprecated requirement | none | crates.io database dump | Yes |
Distribution1 releases, 21,654 downloads over 30 days5 not measured
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| Releases | 1 | crates.io database dump | Yes | |
| Downloads over 30 days | 21654 | crates.io database dump | Yes | |
| Binary downloads over the last 3 releases | Not measured | Yes | ||
| Homebrew installs on request over 365 days | Not measured | Yes | ||
| Repology repository families | Not measured | Yes | ||
| Docker pull growth over 90 days | Not measured | Yes | ||
| Docker pulls at the growth baseline | Not measured | Yes | ||
| Every version a prerelease | false | crates.io database dump | Yes | |
| Every version 0.0.x | false | crates.io database dump | Yes | |
| Every version yanked | false | crates.io database dump | Yes | |
| Crate deleted from crates.io | false | crates.io database dump | Yes |
Repository891 stars, 216 forks, 43 contributors, 2,116 commits. Stars alone never qualify a project.
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| GitHub stars | 891 | GitHub repository | Yes — one part of the repository route | |
| GitHub forks | 216 | GitHub repository | Yes — one part of the repository route | |
| Contributors with a GitHub account | 43 | GitHub contributors | Yes — one part of the repository route | |
| Commits on the default branch | 2116 | GitHub repository | No | |
| Repository's main crate left out of the entry | none | crates.io database dump | Yes |
Facts that never count
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| License | BSD-3-Clause | crates.io database dump | No | |
| Runs on, from listed crates and their direct dependencies | GPU support unknown | crates.io database dump | No | |
| What shows each backend | no dependency or feature matches a backend row | crates.io database dump | No | |
| Native code, from listed crates and their dependencies | No native code found | crates.io database dump | No | |
| Python bindings, from direct dependencies of listed crates | No Python binding crate found | crates.io database dump | No | |
| Crates that depend on a listed crate directly | 3 | crates.io database dump | No |
Corrections and review history
No correction applies to this entry.
Judgments
A judgment enters only through an approved issue and a merged pull request.
No judgment applies to this entry.