Automic VaultAutomic Vault

brew

anchor mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install anchor

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#anchor

nixpkgs package indexes · pkgs/by-name/an/anchor/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Solana Program Framework

Verlauf

Projektgeschichte und Nutzung

Anchor is the Solana Program Framework: a Rust-oriented framework, CLI, IDL system, and client-generation toolchain for building Solana programs. The upstream README calls it the most popular framework for Solana programs.

Projektgeschichte

The public repository was created in January 2021 and describes Anchor as a Solana program framework. Its README lists the major pieces: a Rust eDSL for Solana programs, an IDL specification, a TypeScript package for generated clients, and a CLI for workspace management.

Anchor grew around the full development lifecycle rather than just macros. The docs cover installation, `anchor init`, `anchor build`, `anchor test`, deployment, IDL commands, clients, local validators, and `Anchor.toml` workspace configuration.

The project moved under the Solana Foundation repository namespace while retaining official docs at anchor-lang.com. The latest GitHub release observed for this batch is v1.1.2, published in June 2026.

Adoptionsgeschichte

Anchor's adoption tracks Solana application development: it gives Rust program authors a higher-level account model, generated IDLs, generated TypeScript and Rust client workflows, and a project layout familiar to developers coming from contract frameworks in other ecosystems.

The README explicitly compares the high-level flow to Ethereum tooling such as Solidity, Truffle, and web3.js while noting that Anchor's DSL targets Solana. Official package tables show Anchor components published through crates.io and npm, while the supplied package facts show the CLI available through Homebrew and Nix.

Wie es verwendet wird

Typical usage starts with `anchor init`, then `anchor build`, `anchor test`, and `anchor deploy`. The CLI builds workspace programs for Solana's BPF runtime, emits IDLs under `target/idl`, runs integration tests, and deploys configured programs.

`Anchor.toml` is the central project configuration file. The local-development docs show it specifying clusters and a wallet path such as `~/.config/solana/id.json`, and the CLI docs say commands are configured from the workspace's `Anchor.toml`.

Warum Paket-Nerds sich dafür interessieren

Anchor is significant because it turns a blockchain program into a packageable workspace with a CLI, generated interface files, client packages, and repeatable build/test/deploy commands.

For package managers, the `anchor` command is only one visible edge of a larger toolchain: crates, npm packages, Solana CLI compatibility, AVM, local validator behavior, and project config all need to line up.

Zeitleiste

  • 2021: Public repository created.
  • 2021-2020s: Anchor becomes a standard framework for Solana program development.
  • 2026: Release v1.1.2 published.
  • Current docs: Anchor CLI, Anchor.toml, TypeScript/Rust clients, testing, and deployment are documented at anchor-lang.com.

Related projects

  • Solana CLI: required command-line tooling for Solana development.
  • AVM: Anchor Version Manager, recommended by upstream installation docs.
  • anchor-lang, anchor-spl, and anchor-client: Rust crates published as part of the Anchor ecosystem.
  • @anchor-lang/core and @anchor-lang/cli: npm packages listed by upstream for TypeScript/client and CLI workflows.

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 6 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 1 Build-Abhä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
Anchor.toml

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.config/solana/id.json

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
anchorcliglobales 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-25
Manager-Version1.1.2
Manager aktualisiert2026-07-11
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv1.1.2

https://github.com/otter-sec/anchor

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:anchor
Version1.1.2
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/anchor
Homepagehttps://anchor-lang.com
Repositoryhttps://github.com/otter-sec/anchor
Upstream-Dokumentationhttps://www.anchor-lang.com/docs
LizenzApache-2.0
Quellarchivhttps://github.com/otter-sec/anchor/archive/refs/tags/v1.1.2.tar.gz
Zuletzt aktualisiert2026-07-11T16:26:31-04:00
Pulseupdated
Abhängigkeitenrust
Build-Abhängigkeitenpkgconf
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

anchor

nix profile install nixpkgs#anchor
  • normalized package name match
  • Abgeglichen nach: Anchor
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/an/anchor/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

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.

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
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment