Skip to content

Latest commit

 

History

History
85 lines (60 loc) · 14.4 KB

sources.md

File metadata and controls

85 lines (60 loc) · 14.4 KB

Sources and update procedure

Source baseline reviewed 2026-10-27. config/sources.tsv is the only executable allowlist for native installers, distributions, metadata endpoints, and the Powerlevel10k repository. Editing a link in this document does not change installer behavior. Any source change must also update the manifest fixture and pass the repository checks.

Homebrew formulae and casks use the source declared by their official definitions. The default Doubao flow reads current cask metadata from Homebrew's official JSON API, accepts both its original build-only filename and its current build-plus-release filename, and requires every filename component to match the corresponding cask version field. Optional --with-sogou reads the local cask metadata. Both additionally restrict the resolved URL to its official distribution prefix in sources.tsv and download the fixed-checksum ZIP without installing it.

Installer and configuration sources

Component Executed source Official reference or update entry point
Apple Command Line Tools Local xcode-select --install system installer Apple Xcode resources and macOS Software Update
Homebrew HEAD/install.sh from Homebrew/install brew.sh, installer repository, support tiers
Claude Code, optional https://claude.ai/install.sh with --with-claude Setup and version management, settings
Codex CLI https://chatgpt.com/codex/install.sh CLI installation, configuration
ChatGPT / Codex desktop OpenAI desktop DMG under persistent.oaistatic.com/codex-app-prod/ Desktop app, current ChatGPT cask
Oh My Zsh Official unattended installer with KEEP_ZSHRC=yes, CHSH=no, and RUNZSH=no Unattended installation
Powerlevel10k Shallow clone of the official repository into Oh My Zsh custom themes Oh My Zsh setup, wizard, fonts
Docker Desktop, optional Official arm64 DMG with --with-docker; official cask in managed mode Mac installation, cask
iTerm2 Official Homebrew cask Website, Dynamic Profiles, key mappings
VS Code Official Homebrew cask Website, cask
Obsidian Official Homebrew cask plus a reviewed vault starter Install guide, cask, configuration folders
Google Chrome Official Universal DMG; official cask in managed mode Website, cask definition
Doubao Input Method, default Official ZIP prepared from fixed-checksum cask metadata through the official Homebrew JSON API Website, API, cask
Sogou Input Method, optional Official ZIP prepared from cask metadata Website, release notes, cask
Go Unversioned official Homebrew formula; managed Zsh adds effective GOBIN or every GOPATH/bin macOS installation and PATH, releases, formula
Node.js Homebrew node formula, including npm and npx Downloads, formula
hexyl Homebrew formula Repository, formula
LazyGit Homebrew formula with the lg alias Repository, formula
Fetch tools Fastfetch through its maintained Homebrew formula; Neofetch 7.1.0 from the archived official repository with a fixed SHA-256 Fastfetch formula, Neofetch 7.1.0
Developer fonts font-meslo-lg-nerd-font and font-jetbrains-mono-nerd-font casks MesloLGS, JetBrains Mono
Other command-line tools Official Homebrew formulae listed in formulae.txt https://formulae.brew.sh/formula/<token>

Default mode checks each selected desktop app and downloads an official DMG when it is absent. Docker Desktop requires --with-docker after the user reviews the current vendor terms. iTerm2 and VS Code use casks. AI CLIs prefer official scripts. --managed-desktop enables app placement without selecting Docker.

ChatGPT uses the fixed official DMG path and its appcast. Claude Desktop is accessed only with --with-claude, first through the vendor's latest-DMG redirect and then through the official release feed as a fallback. Chrome and selected Docker Desktop use official rolling DMG addresses. A normal rerun reuses selected packages whose digests still match; --update refreshes them.

Claude Code and Codex use their own native installers and metadata. Recorded hashes support caching and audit; they do not represent an independent vendor signature.

Homebrew checks hashes declared by formulae and casks. Some rolling casks, including Chrome, intentionally use no_check; managed app tests therefore also validate signature, bundle ID, arm64 architecture, and launch behavior. Doubao and Sogou have fixed digests and are saved only after their official URL, checksum, and archive integrity are checked; Doubao also requires the expected vendor-installer layout and confines framework symbolic links to that application tree. Community-maintained casks are packaging metadata, not a claim that every cask is maintained by its software vendor.

Native installer scripts are fetched over HTTPS, hashed for the run record, and then executed. That digest is an audit clue rather than an independent signature or long-term version pin. Never replace allowlisted addresses with an arbitrary mirror, private proxy, or unknown script.

Neofetch is the exception to the rolling-script rule: its upstream repository is archived and current Homebrew no longer provides the formula. One Bite installs the official 7.1.0 script only when no healthy neofetch command exists and rejects any bytes that do not match the SHA-256 in sources.tsv. It never overwrites an unknown broken command. Fastfetch is installed alongside it as the maintained Homebrew-backed alternative.

Input-method installers are kept manual because extracting private components, guessing unattended flags, or writing macOS input-source preferences would bypass the vendor and Apple flows. Package receipts never claim Doubao or Sogou is installed or enabled. Doubao voice input additionally requires the user's microphone decision and an actual speech test.

Chrome automation uses an isolated temporary profile, software rendering, and a test keychain. The test-only --use-mock-keychain flag follows Chrome Launcher's test flags and is never written into the user's browser configuration. See Chrome Headless mode.

Shell, editor, and terminal sources

  • VS Code extensions are installed through the official CLI from Marketplace. The declared list contains Go, Python, Ruff, ESLint, Prettier, YAML, ShellCheck, and Microsoft's Sublime Text keymap. Publishers vary; the list is not entirely Microsoft-maintained.
  • iTerm2 configuration uses official Dynamic Profiles and profile color fields. The One Bite profile has its own stable GUID and selects the installed MesloLGS Nerd Font by PostScript name. iTerm2 deliberately removes the deprecated Default Bookmark field from dynamic profiles, so One Bite manages the documented global default GUID separately and preserves a later user override.
  • CODEX_HOME and CLAUDE_CONFIG_DIR choose their configuration directories. One Bite accepts existing absolute paths. Finder-launched apps cannot be assumed to inherit terminal environment variables.
  • Powerlevel10k is installed after Oh My Zsh and does not replace an explicit theme. Run p10k configure in a newly opened One Bite profile; it creates the user-owned ~/.p10k.zsh. Existing terminal windows and unrelated profiles keep their font selection.
  • The Obsidian starter uses portable vault-local settings documented by Obsidian. Its bundled Tokyo Night theme is version 1.1.7 from the official community-theme repository and retains its MIT license. The wide snippet is a small One Bite setting. Workspace state, private notes, account data, and community plugin data are excluded.
  • env.zsh sets DOCKER_DEFAULT_PLATFORM to linux/amd64 when it was not already set. This engine-neutral client setting remains useful with Docker Desktop, another compatible local engine, or a remote Docker context; a project or one-off command can set a different architecture. Services such as the qBittorrent launcher pass their runtime platform explicitly.

Homebrew trust and network policy

Homebrew 6 loads official definitions and explicitly trusted third-party formulae under its tap trust policy. Warnings from a user's Bun, Turso, or other tap do not affect the official Go formula. One Bite never trusts an entire unrelated tap or removes user sources just to hide a warning.

The documented HOMEBREW_CURLRC interface accepts an absolute curl configuration. One Bite selects public config/download.curlrc only when the variable is unset, preserving private proxy, certificate, and trust settings. The default forces HTTP/1.1 to avoid observed HTTP/2 protocol failures while retaining HTTPS and certificate validation. Direct curl downloads and diagnostics use the same timeout and retry policy based on the curl options. It exits predictably on failure and never changes mirrors or disables TLS.

Diagnostics query only connectivity entries in sources.tsv: Homebrew API, GitHub, GHCR, npm, and selected AI installer endpoints. Requests have connection and total timeouts, send no API key, do not print proxy addresses, and use no IP-discovery service. HTTP 401, 403, or 429 proves reachability but not authorization or quota. TLS, DNS, connection, and server failures are reported. Install mode warns and proceeds to the concrete operation; --diagnose returns nonzero for failed probes. A failed final download or verification always fails the install.

Update metadata

--check-updates reads only maintenance-* entries from sources.tsv. Package queries use the public Homebrew API; Homebrew itself uses official release metadata. The check does not run brew update, and an installed version ahead of the catalog is preserved.

VS Code querying follows Microsoft's extension gallery implementation: request public IDs, reject prereleases, and filter for arm64 or universal artifacts. The report exposes engine requirements while the VS Code CLI decides actual compatibility. Git sources use ls-remote without fetching or changing the worktree.

Maintainer checklist

  1. Read the vendor's current installation, configuration, platform, and release documentation.
  2. Update sources.tsv, package manifests, or templates without adding credentials.
  3. Bump only the patch version. Update repository-files.txt for file-set changes and deliberately regenerate the complete configuration golden fixture.
  4. Stage reviewed paths and run make check for build, regression tests, format checks, and archive validation.
  5. Test fresh and existing installs, skip behavior, preservation, and recovery on a disposable runner; never perform a destructive full install test on a daily-use Mac.
  6. Create and push an annotated v<VERSION> tag for the verified commit; never move an existing release tag.
  7. Compare inventory and download reports and trust actual logged versions rather than historical examples in documentation.
  8. Claim Docker engine and GUI keyboard behavior only after testing them on the target physical Mac.

A pinned One Bite commit fixes its process, templates, package set, and verification rules. Upstream stable and latest channels still move. Reports make changes traceable but cannot guarantee byte-identical third-party software at every future date. Long-term binary reproducibility requires separately archiving vendor artifacts and hashes after reviewing redistribution rights; One Bite does not secretly cache or republish them.

The default Charm tools Glow, Pop, Gum, and Crush come from the official Charm tap. One Bite trusts those formulae individually rather than the whole tap, and update checks parse generated version/revision declarations without executing remote Ruby.