Automic VaultAutomic Vault

brew

yor mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install yor

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#yor

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

Überblick

Paketzusammenfassung

Extensible auto-tagger for your IaC files

Befehle und Aliase

  • yor

Verlauf

Projektgeschichte und Nutzung

Yor is Bridgecrew's open-source auto-tagger for infrastructure-as-code files. It adds consistent tags and trace identifiers to Terraform, CloudFormation, Serverless Framework, and related IaC so cloud resources can be traced back to code, owners, commits, and change history.

Projektgeschichte

Yor was publicly launched on 2021-05-27, shortly after Palo Alto Networks acquired Bridgecrew. Palo Alto's announcement framed it as an open-source IaC tag-and-trace tool for developer workflows, with local CLI, pre-commit, GitHub Actions, and CI/CD usage.

The README describes Yor as an open-source tool that adds informative and consistent tags across IaC frameworks, with built-in support for Terraform, CloudFormation, and Serverless Frameworks, plus custom taggers, skip annotations, dry runs, and Git-based tags.

Adoptionsgeschichte

Yor's adoption story is tied to cloud governance rather than app deployment. Help Net Security covered it as a tool for traceability and auditability, noting that organizations can run it retroactively across infrastructure resources or build it into CI/CD so ownership and other tags come from IaC and git history.

Packaging followed developer workflow channels: Homebrew, Chocolatey, Docker, GitHub Actions, Azure DevOps snippets, and pre-commit hooks are all documented entry points.

Wie es verwendet wird

The common command is `yor tag --directory terraform/`, with options to recurse or not, include or skip tag groups, target specific frameworks, add simple custom tags, preview with dry-run, write JSON output, and skip directories or resource types.

The most package-relevant mode is automated CI: Yor can run as a GitHub Action or pre-commit hook that modifies IaC files so trace and owner tags travel from source repositories into provisioned cloud resources.

Warum Paket-Nerds sich dafür interessieren

Yor matters because it packages cloud tagging policy as a repeatable source-code transformation. It is a small CLI, but its runtime effect is on Terraform and other IaC files that later become cloud inventory, billing, security, and incident-response metadata.

It is also an example of DevSecOps tooling where the package manager is part of governance distribution: install the CLI in CI, pin the hook/action version, and every repository can apply the same tagging logic.

Zeitleiste

  • 2021-05-27: Palo Alto Networks announces Yor as an open-source automated IaC tag-and-trace tool.
  • 2021-05-27: Security press covers Yor as an IaC traceability and auditability tool built by Bridgecrew.
  • 2020s: Yor documents usage as CLI, Docker image, GitHub Action, Azure DevOps step, and pre-commit hook.

Related projects

  • Bridgecrew and Prisma Cloud/Cortex Cloud are the commercial ecosystem around the project.
  • bridgecrewio/yor-action is the GitHub Action integration.
  • Terraform, CloudFormation, Serverless Framework, Kubernetes, pre-commit, Docker, and GitHub Actions are major adjacent technologies in documented 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 8 Plattformziele verfügbar.
  • 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.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
yorcliglobales 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-Version0.1.200
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Version0.1.200

https://github.com/bridgecrewio/yor

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:yor
Version0.1.200
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/yor
Homepagehttps://yor.io/
Repositoryhttps://github.com/bridgecrewio/yor
Upstream-Dokumentationhttps://yor.io/
LizenzApache-2.0
Quellarchivhttps://github.com/bridgecrewio/yor/archive/refs/tags/0.1.200.tar.gz
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

Nix95%

yor

nix profile install nixpkgs#yor
  • normalized package name match
  • Abgeglichen nach: Yor
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/yo/yor/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 package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment