macOS
Homebrewverified · 100%
brew install js-beautifylocal Homebrew formula metadata
brew / rank 4468
Install js-beautify with Homebrew, Nix
JavaScript, CSS and HTML unobfuscator and beautifier. Version 2.0.3 via Homebrew; verified 2026-07-01. Also installable with nix: nix profile install nixpkgs#js-beautify.
install
Additional install commands
Linux
Nixverified · 92%
nix profile install nixpkgs#js-beautifynixpkgs package indexes · pkgs/by-name/js/js-beautify/package.nix · source: api.github.com
overview
Package summary
JavaScript, CSS and HTML unobfuscator and beautifier
Project links
Commands and aliases
- css-beautify
- html-beautify
- js-beautify
history
Project history and usage
JS Beautifier, distributed as js-beautify, is a formatter and de-obfuscation tool for JavaScript, JSON, CSS, SCSS, HTML, and related web syntaxes. It predates the formatter monoculture around Prettier and remains a familiar CLI and web tool for turning minified or packed frontend code back into readable source.
Project history
The GitHub repository was created in December 2008, and the README describes the tool as a way to reformat bookmarklets, ugly JavaScript, scripts packed by Dean Edwards' packer, and output from JavaScript obfuscators. The project grew from JavaScript beautification into a multi-language web-source formatter with command-line binaries for JavaScript, CSS, and HTML.
The npm package history begins in July 2012 and shows steady releases across the 1.x line for more than a decade. The project also maintains beautifier.io as the browser-facing interface, making the same lineage visible both to CLI users and to developers pasting code into an online beautifier.
Adoption history
JS Beautifier spread through npm, Homebrew, and direct browser use because it solved a common web-development task before formatter-on-save workflows were standard. Its GitHub repository has thousands of stars and many forks, and the package-manager footprint reflects long-lived demand for a simple beautify/unobfuscate command.
How it is used
The CLI is used to re-indent source files, inspect minified production JavaScript, normalize generated HTML or CSS, and run formatter settings from a .jsbeautifyrc file. It is more of a readability and recovery tool than a modern opinionated style enforcer.
Why package nerds care
js-beautify is significant because it captures an earlier era of JavaScript tooling: before bundlers, minifiers, linters, and opinionated formatters all converged into modern frontend toolchains, a small beautifier package could become infrastructure for editors, web tools, distro packages, and debugging workflows.
Timeline
- 2008: GitHub repository created for js-beautify.
- 2012: npm package publication history began with 0.1.8.
- 2013: 1.x releases established the package as a stable CLI-era JavaScript beautifier.
- 2024: 1.15.0 shipped in the long-running 1.x release line.
- 2026: 2.x releases appeared on npm and the beautifier.io interface identified itself with the 2.x line.
Related projects
- Related projects include beautifier.io, the Python jsbeautifier distribution, Prettier, ESLint formatting workflows, Dean Edwards' packer, and other source beautifiers embedded in editors and web debugging tools.
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.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Unix
.jsbeautifyrc
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
css-beautify | executable | indexed executable | Discovered from the local executable index. |
html-beautify | executable | indexed executable | Discovered from the local executable index. |
js-beautify | 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 version2.0.3
manager updated2026-07-01
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:js-beautify |
|---|---|
| Version | 2.0.3 |
| Package manager | Homebrew |
| Homepage | https://beautifier.io |
| Last updated | 2026-07-01T18:24:39Z |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source database matches
Other package-manager records
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
Nix95%
js-beautify
nix profile install nixpkgs#js-beautify- normalized package name match
- Matched by: Js Beautify
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
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- external package-manager database matches
- pkg.so package database
- pkgdb category and tag curation