Polyglot Utilities Toolkit
One practical place to find small, reusable utilities across languages. This project groups utilities by capability first and language second, so you can find the behavior you need without learning a separate repository for every language.
Browse the examples · Cross-language grouping tutorial · Find a starter task · Contributing guide
Try a utility in under a minute
The toolkit includes a unique collection helper that removes duplicate values while preserving their first occurrence.
JavaScript
import { unique } from "./utilities/collections/javascript/collection_utils.js";
console.log(unique([3, 1, 3, 2, 1]));
// [3, 1, 2]
Run the JavaScript compatibility tests from the repository root:
node --experimental-default-type=module tests/matrix/javascript/test_matrix.mjs
Python
from utilities.collections.python.collection_utils import unique
print(unique([3, 1, 3, 2, 1]))
# [3, 1, 2]
Run the Python compatibility tests from the repository root:
python -m unittest discover -s tests/matrix/python -p "test_*.py"
You only need the toolchain for the language you're working on. See Getting Started for more languages and commands.
What you'll find
Utilities are grouped by capability, with language-specific implementations inside each capability.
| Capability | What it covers |
|---|
| Collections | Reusable operations on lists and collections |
| Strings | Common string transformations and helpers |
| Numbers | Numeric helpers and boundary behavior |
| Dates | Date-related helpers |
| Validation | Reusable validation rules |
| Forms, models, runtime | Focused helpers for applicable environments |
Current implementations include TypeScript, JavaScript, Python, C++, Java, Go, Rust, C#, and Kotlin. Coverage differs by capability and language; check the cross-language test matrix rather than assuming every utility exists everywhere.
Make your first contribution
You do not need to understand every language or install every toolchain.
- Browse good first issues or all open issues.
- Choose a task with a clear scope in one language or one documentation file.
- For a typo, example, or other small, self-contained fix, you can open a PR directly. For a larger change, comment on the issue first so we can avoid duplicate work.
- Follow the contributor guide, run the relevant check, and include the command and result in your PR.
First-time contributors are welcome. If an issue's scope is unclear, ask a question before investing time.
Project guides
Design principles
- Capability is the primary organizational boundary; language is the implementation boundary.
- Equivalent utilities should align in observable behavior without forcing identical APIs.
- Framework-specific code stays separate from general-purpose utilities.
- Existing behavior should be preserved when utilities are reorganized.
- Code remains free of comments; examples may include comments to explain their output.
Development notes
TypeScript tooling is available for TypeScript utilities and React integrations. Other languages use their normal toolchains. Java capability implementations are independent Maven projects targeting Java 17; Go implementations are independent Go modules; Rust implementations are independent Cargo packages; C# projects target .NET 8; and Kotlin projects use Gradle Kotlin DSL.
Compatibility verification is currently manual. See the test matrix guide for canonical cases, runners, and language-specific verification.
License
This project is licensed under the MIT License. You may use, modify, and distribute the software subject to the license terms.
