macOS
Homebrewvérifié · 100%
brew install autocodelocal Homebrew formula metadata
brew
Installer autocode avec Homebrew
Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de autocode pour les workflows d'agents IA.
installation
Commandes d'installation supplémentaires
aperçu
Résumé du paquet
Code automation for every language, library and framework
Liens du projet
Commandes et alias
- autocode
historique
Historique du projet et usages
Autocode was an npm-distributed, spec-driven code generator with hosted ReadMe documentation and a GitHub-integrated workflow for generating APIs, apps, websites, and project files from configuration.
Historique du projet
The npm registry records the autocode package as created on 13 November 2014, version 1.0.0 as published on 27 October 2015, and version 1.3.1 as published on 18 February 2016. The official ReadMe-hosted introduction describes it as a hackable, spec-driven code generator for producing code in any language or format.
The official docs place Autocode in the mid-2010s wave of hosted developer tools around GitHub OAuth, generated project structure, and npm-distributed CLIs. They describe a web UI with areas for globals, imports, exports, outputs, interfaces, scripts, config, and files, plus hacking concepts such as generators, schemas, specs, engines, helpers, processors, transformers, and injectors.
The npm registry metadata for version 1.3.1 lists a GitHub repository under ctate/autocode, but that URL returned HTTP 404 during review. Since no official live HTTP source-control page could be verified, the repository should remain null rather than inferred from stale registry metadata.
Historique d'adoption
Autocode's official documentation was written around GitHub login: users could create or load repositories and immediately begin generating code for them, with the service requesting read/write access to public and private repositories. That reflects a hosted-code-generation model rather than a purely local compiler or scaffolder.
Its adoption footprint is best understood as narrow and historical. The package survives as an npm tarball and package-manager formula, while the public source repository and hosted product context are much harder to verify than the ReadMe documentation and registry metadata.
Modes d'utilisation
The documentation describes using Autocode to define specs and outputs, generate code, build and run code, export generators and schemas, and edit configuration through a Config tab. Examples include JSON generation/parsing, Express apps, package-manager files, README files, Redis config, and framework-specific project outputs.
The package's practical config convention is `.autocode/config.yml`, visible in official examples and package-manager tests. That config-driven design is the key package-nerd detail: the CLI is a front end to generated outputs described by structured project data rather than a single language compiler.
Pourquoi les passionnés de paquets s'y intéressent
Autocode is a package-history oddity: an old npm package and CLI for a hosted code-generation workflow whose original repository URL no longer resolves. It is a good case where npm metadata, hosted docs, and package-manager records outlive the active source project.
For enrichment, the lazy safe move is to cite the registry and official docs, keep the stale repository out of the official repo field, and avoid inventing continuity with newer unrelated projects that share the same name.
Chronologie
- 2014-11-13: npm registry created the autocode package.
- 2015-10-27: version 1.0.0 published to npm.
- 2016-02-18: version 1.3.1 published to npm.
- 2022-06-13: npm registry metadata modified.
- 2026-07-02: The registry-listed ctate/autocode GitHub URL returned HTTP 404 during review.
Related projects
- GitHub is central to the official login and repository workflow.
- The docs describe generators, schemas, specs, engines, processors, transformers, and injectors as Autocode customization concepts.
- ReadMe hosts the surviving official documentation surface.
Sources
posture de sécurité
Niveau de risque : vert
library-like package without higher-risk signals.
Classificateur de risque
risque vert · confiance faible · appliance
Pourquoi
- library-like package without higher-risk signals
Signaux
- metadata:library-like
Comportement d'installation
- Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
- Les métadonnées de bottle Homebrew sont disponibles pour 13 plateformes.
- S’installe avec 1 dépendances d’exécution.
Revue recommandée
Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des 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
.autocode/config.yml
exécutables
Exécutables installés
| Commande | Type | Exposition | Note |
|---|---|---|---|
autocode | cli | exécutable global |
fraîcheur
Version et fraîcheur
Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.
page générée2026-07-26
version du gestionnaire1.3.1
gestionnaire mis à jour
données localesOK
amontnot checked
dernière version détectéenon détecté
- infoNo package-manager update timestamp was available.confiance faible
- infoRelease/tag comparison is only available for GitHub repositories.https://autocode.readme.io/confiance none
métadonnées d'installation
Métadonnées du paquet
| Clé du paquet | brew:autocode |
|---|---|
| Version | 1.3.1 |
| Gestionnaire de paquets | Homebrew |
| Page du gestionnaire de paquets | https://formulae.brew.sh/formula/autocode |
| Page d'accueil | https://autocode.readme.io/ |
| Docs amont | https://autocode.readme.io/docs/config |
| Licence | Apache-2.0 |
| Archive source | https://registry.npmjs.org/autocode/-/autocode-1.3.1.tgz |
| Dépendances | node |
| Bouteille | disponible (sur arm64_big_sur, arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, big_sur, catalina, monterey, sonoma, ventura, x86_64_linux) |
| post-install Homebrew | non défini |
| Service | aucun déclaré |
faits du registre
Détails de la base source
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | autocode |
| Version Scheme | 0 |
| Revision | 0 |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
piste source
Généré depuis les données du dépôt
Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Sources utilisées
- 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