macOS
Homebrewverifiziert · 100%
brew install autorestlocal Homebrew formula metadata
brew
autorest mit Homebrew installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für autorest in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Überblick
Paketzusammenfassung
Swagger (OpenAPI) Specification code generator
Projektlinks
Befehle und Aliase
- autorest
Verlauf
Projektgeschichte und Nutzung
AutoRest is Microsoft's OpenAPI/Swagger code generation tool for producing client libraries and SDKs, especially around Azure. It turns OpenAPI descriptions plus configuration files into generated code for languages such as C#, Java, Python, TypeScript, Go, PowerShell, and others.
Projektgeschichte
The Azure/autorest repository was created in February 2015. Official repository metadata describes it as an OpenAPI, formerly Swagger, specification code generator supporting multiple languages.
AutoRest evolved around a configuration-heavy model. The official docs emphasize command-line flags, YAML/JSON/Markdown configuration files, and literate readme.md files that combine human documentation with machine-readable generation settings.
Adoptionsgeschichte
AutoRest adoption is strongly tied to Azure SDK generation and the azure-rest-api-specs repository. The official generation docs reference Azure SDK language repositories and management-plane generation, showing that AutoRest became infrastructure for large-scale, multi-language SDK production rather than just a standalone end-user CLI.
The Homebrew input lists only a Homebrew package for this batch, but official GitHub metadata shows thousands of stars and hundreds of forks for Azure/autorest, consistent with a prominent role in Azure developer tooling.
Wie es verwendet wird
Basic usage is autorest with an input OpenAPI file and a language flag, for example autorest --input-file=pets.json --python --output-folder=myFolder/. The preferred documented workflow moves those options into a configuration file and runs autorest readme.md.
AutoRest supports YAML, JSON, and Markdown configuration. Markdown literate configuration is especially important: docs say readme.md can serve as both project documentation and the storage for generation settings, using code blocks and the magic string that identifies AutoRest configuration.
Warum Paket-Nerds sich dafür interessieren
AutoRest matters to package nerds because it is generator infrastructure at cloud-provider scale. It explains why SDK repositories can contain large generated surfaces, language-specific generator packages, pinned core versions, and readme.md files that are executable configuration rather than just documentation.
Zeitleiste
- 2015: Azure/autorest GitHub repository created.
- 2010s: AutoRest becomes associated with Swagger/OpenAPI-based Azure SDK generation.
- 2020s: AutoRest docs emphasize multi-language generation, literate configuration, and Azure management-plane workflows.
Related projects
- azure-rest-api-specs supplies many OpenAPI inputs used with AutoRest.
- Azure SDK language repositories consume generated output from AutoRest workflows.
- OpenAPI/Swagger is the specification family AutoRest reads.
Quellen
Sicherheitslage
Risikostufe: grün
narrow executable package without higher-risk signals.
Risikoklassifikator
grün Risiko · niedrig Konfidenz · appliance
Warum
- narrow executable package without higher-risk signals
Signale
- metadata:no-higher-risk-signals
Installationsverhalten
- In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
- Homebrew-Bottle-Metadaten sind für 1 Plattformziele verfügbar.
- Installiert mit 1 Laufzeitabhängigkeiten.
Empfohlene Prüfung
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
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
./readme.md./*.md./*.markdown<config-file>.md<config-file>.json<config-file>.yaml
Executables
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
autorest | cli | globales Executable |
Aktualität
Version und Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
Seite generiert2026-07-08
Manager-Version3.8.0
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt
https://github.com/Azure/autorest
- InfoNo package-manager update timestamp was available.niedrig Konfidenz
- InfoNo cached GitHub release or tag data was available.https://github.com/Azure/autorestnone Konfidenz
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | brew:autorest |
|---|---|
| Version | 3.8.0 |
| Paketmanager | Homebrew |
| Paketmanager-Seite | https://formulae.brew.sh/formula/autorest |
| Homepage | https://github.com/Azure/autorest |
| Repository | https://github.com/Azure/autorest |
| Upstream-Dokumentation | https://github.com/Azure/autorest#readme |
| Lizenz | MIT |
| Quellarchiv | https://registry.npmjs.org/autorest/-/autorest-3.8.0.tgz |
| Abhängigkeiten | node |
| Bottle | verfügbar (auf all) |
| Homebrew post-install | nicht definiert |
| Dienst | keiner deklariert |
Registry-Fakten
Details aus der Quelldatenbank
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | autorest |
| Version Scheme | 0 |
| Revision | 0 |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
Quellspur
Aus Repository-Daten generiert
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
Combined YAML source
View the package source record on GitHub.
Verwendete Quellen
- Geiger risk classifier
- Nucleus package database
- av.db category and tag curation
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- package relationship graph
- package version freshness
- package-page enrichment