# tscriptify mit Homebrew installieren

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

## Installation

```sh
sudo av install brew:tscriptify
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install tscriptify
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:tscriptify
- **Paketmanager:** Homebrew
- **Version:** 0.2.0
- **Quellzusammenfassung:** Golang struct to TypeScript class/interface converter
- **Homepage:** <https://github.com/tkrajina/typescriptify-golang-structs>
- **Repository:** <https://github.com/tkrajina/typescriptify-golang-structs>
- **Zuletzt aktualisiert:** 2026-07-26T00:51:28+02:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- tscriptify (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

tscriptify is a small Go developer tool for generating TypeScript classes or interfaces from Go structs, especially structs whose JSON tags define API payload shapes.

### Projektgeschichte

The project is published as tkrajina/typescriptify-golang-structs and describes itself as a Go JSON-to-TypeScript model converter. Its README documents both a command-line tool, installed with `go install github.com/tkrajina/typescriptify-golang-structs/tscriptify`, and a Go library package.

The official changelog records early 0.1.x work around custom types, enum generation, pointer handling, interface output, Go modules, packages with hyphens, TypeScript doc tags, and matrix testing. That history points to a focused utility maintained around practical Go-to-TypeScript model generation rather than a broad framework.

### Adoptionsgeschichte

Its package-manager footprint in this batch is Homebrew only, which fits the tool's niche: developers installing a small CLI when a Go backend and TypeScript frontend need matching model definitions.

### Wie es verwendet wird

The README's main CLI pattern is `tscriptify -package=... -target=... Model1 Model2`, with optional import strings and support for converting all structs in a Go file. It can also be embedded through the Go API by constructing a converter and writing generated models to a TypeScript file.

The converter relies on Go struct fields with JSON tags, supports class and interface style output, handles custom TypeScript snippets, and exposes command-line options for package, target, and backup directory.

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

For package-manager users, tscriptify is the kind of narrow CLI that earns a formula because it removes build-step friction in polyglot Go and TypeScript projects. Its importance is practical rather than ecosystem-defining: install it, point it at backend structs, and keep frontend model definitions synchronized.

### Zeitleiste

- 0.1.0: Changelog records simplified conversion, maps of objects, custom imports, pointer optional fields, and enum handling.
- 0.1.5: Changelog records Go module support and a JSON-to-TypeScript model shell-script example.
- 0.1.8-0.1.9: Changelog records TypeScript doc tags, handling fields without JSON tags, and matrix testing.

### Related projects

- The project sits in the Go code-generation family alongside tools that generate client models or API bindings from backend definitions, but its official documentation keeps the scope specifically to Go structs and TypeScript models.

### Quellen

- <https://github.com/tkrajina/typescriptify-golang-structs#readme>
- <https://github.com/tkrajina/typescriptify-golang-structs/blob/master/CHANGELOG.md>
- source_facts.package-manager


## Sicherheitshinweise

narrow executable package without higher-risk signals.

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


## Combined YAML source

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


## Quellen

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