# json2ts mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für json2ts in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:json2ts
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install json2ts
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#json2ts
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/js/json2ts/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:json2ts
- **Paketmanager:** Homebrew
- **Version:** 15.0.4
- **Quellzusammenfassung:** Compile JSONSchema to TypeScript type declarations
- **Homepage:** <https://github.com/bcherny/json-schema-to-typescript>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- json2ts (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 15.0.4
## Projektgeschichte und Nutzung

json-schema-to-typescript is a TypeScript and Node.js code-generation tool that compiles JSON Schema documents into TypeScript declaration files. The Homebrew package is named json2ts after its command-line executable.

### Projektgeschichte

Boris Cherny's repository was created in March 2016, and the npm package metadata records the first `0.1.0` publication on March 31, 2016. The project appeared as TypeScript was becoming a common way to describe JavaScript APIs while JSON Schema remained a common contract format for data validation.

The package evolved from a CLI into both a CLI and programmatic API. Its README documents `json2ts` usage for stdin, files, directories, globbed schema trees, YAML input, and library calls such as `compile` and `compileFromFile`.

### Adoptionsgeschichte

The repository had thousands of GitHub stars by 2026 and the npm registry recorded more than one hundred published versions. Its adoption came from teams that already had JSON Schema contracts and wanted generated `.d.ts` files rather than hand-maintained TypeScript interfaces.

### Wie es verwendet wird

The common package-manager path is to install the Node package or Homebrew formula, then run `json2ts` to transform JSON or YAML schemas into TypeScript declarations. It can also be embedded in build scripts through the JavaScript API.

### Warum Paket-Nerds sich dafür interessieren

json2ts is package-nerd notable because it is a bridge between schema-first JSON tooling and TypeScript's static type ecosystem. It shows how a Node package can become a CLI distributed through npm and system package managers when the executable is useful outside JavaScript projects.

### Zeitleiste

- 2016-03-22: The GitHub repository was created.
- 2016-03-31: npm recorded version 0.1.0 for `json-schema-to-typescript`.
- 2016-07-22: npm recorded version 1.0.0.
- 2025-01-14: npm metadata showed package modification after many published versions.

### Related projects

- The project is related to JSON Schema, TypeScript declaration generation, `typescript-json-schema` for the reverse direction, and schema-aware API tooling that uses JSON Schema as the source of truth.

### Quellen

- <https://formulae.brew.sh/formula/json2ts>
- <https://github.com/bcherny/json-schema-to-typescript>
- <https://github.com/bcherny/json-schema-to-typescript/blob/master/package.json>
- <https://registry.npmjs.org/json-schema-to-typescript>
- <https://www.npmjs.com/package/json-schema-to-typescript>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals

## Andere Paketmanager-Einträge

- Nix - json2ts: normalized package name match | nixpkgs package indexes: pkgs/by-name/js/json2ts/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/json2ts.yml](https://github.com/mxcl/pkgdb/blob/main/combined/json2ts.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph