Automic VaultAutomic Vault

brew

Install autocode with Homebrew

Code automation for every language, library and framework. Version 1.3.1 via Homebrew; verified from local package data.

Install commandSecurity notes

install

Additional install commands

macOS

Homebrewverified · 100%
brew install autocode

local Homebrew formula metadata

overview

Package summary

Code automation for every language, library and framework

Commands and aliases

  • autocode

history

Project history and usage

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.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

  • 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.

security posture

Risk level: green

library-like package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • library-like package without higher-risk signals

Signals

  • metadata:library-like

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 13 platform targets.
  • Installs with 1 runtime dependencies.

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
.autocode/config.yml

executables

Installed executables

CommandKindExposureNote
autocodecliglobal executable

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-07-26
manager version1.3.1
manager updated
local dataok
upstreamnot checked
latest detectednot detected

https://autocode.readme.io/

  • infoNo package-manager update timestamp was available.low confidence
  • infoRelease/tag comparison is only available for GitHub repositories.https://autocode.readme.io/none confidence

install metadata

Package metadata

Package keybrew:autocode
Version1.3.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/autocode
Homepagehttps://autocode.readme.io/
Upstream docshttps://autocode.readme.io/docs/config
LicenseApache-2.0
Source archivehttps://registry.npmjs.org/autocode/-/autocode-1.3.1.tgz
Dependenciesnode
Bottleavailable (on arm64_big_sur, arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, big_sur, catalina, monterey, sonoma, ventura, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameautocode
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

Related tools

  • nodeRuntime dependency declared by Homebrew.

Same workflow

  • apibuilder-cliShares av.db curated category or tags: cli, code-generation, developer-tools.
  • asn1cShares av.db curated category or tags: cli, code-generation, developer-tools.
  • asyncapiShares av.db curated category or tags: cli, code-generation, developer-tools.
  • autogenShares av.db curated category or tags: cli, code-generation, developer-tools.
  • autorestShares av.db curated category or tags: cli, code-generation, developer-tools.
  • bindgenShares av.db curated category or tags: cli, code-generation, developer-tools.

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.

Used sources

  • 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