macOS
brew install jimtclprovider-native install command
brew / rank 5218
Small footprint implementation of Tcl. Version 0.84 via Homebrew; verified 2026-07-30.
install
brew install jimtclprovider-native install command
overview
Small footprint implementation of Tcl
history
Jim Tcl is a small-footprint implementation of Tcl intended for embedding, standalone scripting through `jimsh`, and systems where the full Tcl distribution is too large. Its manual describes a Tcl 8.5-compatible core with many Tcl 8.6 commands, optional modules, object-based I/O, sockets, integer, dict, and operating-system features.
Jim Tcl began in January 2005 as Salvatore Sanfilippo's experiment in hacking on Tcl. The project README says that after about a month it could run simple scripts, and after about two months it had grown beyond a disposable toy into a candidate real interpreter, with early contributions from Pat Thoyts and Clemens Hintze.
The project later developed into an embeddable interpreter with optional extensions, a modular build, and the `jimsh` command shell. Its copyright and maintainer notes show a wider contributor base by 2008 and Steve Bennett as maintainer, while the release stream and reference manual show continuing work through the 0.8x series.
Jim Tcl's most visible adoption came from embedded and systems tooling. OpenOCD documents that it uses Jim Tcl as its command interpreter, that OpenOCD configuration scripts are Jim Tcl scripts, and that OpenOCD commands extend Jim Tcl. That made Jim Tcl part of the toolchain used by developers working with on-chip debugging and microcontroller boards.
Jim Tcl can be linked into applications with `cc <source> -ljim`, used interactively with `jimsh`, or used to run Tcl scripts from files, standard input, or `jimsh -e`. The README frames its use cases as scriptable applications, embedded systems, configuration-file-like syntax, and a compact Tcl implementation that can be shipped inside another program.
Jim Tcl is package-nerd catnip because it is a language runtime small enough to show up as both an application dependency and a standalone shell. It explains why some packages depend on `jimsh` or `jimtcl` rather than full Tcl: the value is a Tcl-like extension language in roughly hundreds of kilobytes, with feature selection controlled at build time.
security posture
narrow executable package without higher-risk signals.
green risk · low confidence · appliance
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
build-jim-ext | executable | indexed executable | Discovered from the local executable index. |
jimdb | executable | indexed executable | Discovered from the local executable index. |
jimsh | executable | indexed executable | Discovered from the local executable index. |
freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
install metadata
| Package key | brew:jimtcl |
|---|---|
| Version | 0.84 |
| Package manager | Homebrew |
| Homepage | https://jim.tcl.tk/index.html |
| Repository | https://github.com/msteveb/jimtcl |
| Last updated | 2026-07-30T22:31:03+09:00 |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source trail
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
View the package source record on GitHub.