macOS
Homebrewverified · 100%
brew install kutoprovider-native install command
brew / rank 7014
Install kuto with Homebrew
Reverse JS bundler. Version 0.3.6 via Homebrew; verified 2026-06-13.
install
Additional install commands
overview
Package summary
Reverse JS bundler
Project links
Commands and aliases
- kuto
history
Project history and usage
Kuto is a small reverse JavaScript bundler that experiments with reusing code a client has already downloaded, especially for large ESM bundles.
Project history
Sam Thor published Kuto publicly with a March 2024 explanation of the idea: split a built JavaScript bundle into a main file plus cacheable corpus files, then reuse unchanged corpus code across later builds. The README says the `kuto info` command came first as a way to inspect ES modules for side effects.
Adoption history
Kuto is a niche web-performance tool rather than a mainstream bundler replacement. Its own documentation frames it as a final pass after another bundler and asks users for real-world results, which matches a young experimental tool.
How it is used
The CLI is used after bundling: `kuto split` reads a large ESM output file, writes a main part plus static corpus files, and can use previously generated output as the old corpus for later builds.
Why package nerds care
Kuto is interesting to package and web-build-system nerds because it reverses the usual bundling assumption. Instead of making one fresh optimized artifact per build, it tries to preserve previously shipped code as a reusable cache dictionary.
Timeline
- March 2024: Maintainer published the reverse-bundler write-up and linked it from the project README.
- Initial design: `kuto info` originated as an ES module side-effect inspection command before the split workflow.
Related projects
- Kuto is designed to run after conventional JavaScript bundlers, and its README demonstrates a release process that uses esbuild before and after Kuto.
Sources
security posture
Risk level: green
narrow executable package without higher-risk signals.
Risk classifier
green risk · low confidence · appliance
Why
- narrow executable package without higher-risk signals
Signals
- metadata:no-higher-risk-signals
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
kuto | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and 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.
page generated2026-08-03
manager version0.3.6
manager updated2026-06-13
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:kuto |
|---|---|
| Version | 0.3.6 |
| Package manager | Homebrew |
| Homepage | https://github.com/samthor/kuto |
| Last updated | 2026-06-13T23:35:01+02:00 |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- Nucleus package database
- curated package history
- pkgdb category and tag curation