pkg.soopen package index

brew / Rang 2458

oauth2l mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install oauth2l

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#oauth2l

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

Überblick

Paketzusammenfassung

Simple CLI for interacting with Google oauth tokens

Befehle und Aliase

  • oauth2l

Verlauf

Projektgeschichte und Nutzung

oauth2l, pronounced "oauth tool" in its README, is Google's Go CLI for fetching, printing, inspecting, testing, and using Google OAuth 2.0 access tokens from shell workflows. It is narrower than generic OAuth clients, but deeper in Google-specific authentication paths such as Google Cloud SDK credentials, Google Compute Engine and Google Kubernetes Engine service accounts, service-account JSON keys, domain-wide delegation examples, and cached local tokens.

Projektgeschichte

The google/oauth2l repository was created on 2016-03-31, making it one of the older maintained Go CLIs in this batch. Its README frames the project around the practical problem of turning Google OAuth credentials into command-line access tokens that can be passed to tools such as curl.

The project's 2022-07-19 v1.3.0 release was a security-oriented milestone: release notes added the three-legged OAuth loopback flow and PKCE support, replacing the deprecated copy-and-paste out-of-band pattern with a localhost redirect flow managed by oauth2l. Later releases in 2024 and 2025 focused on arm64 packaging, README updates, dependency upgrades, and vulnerability-scanner cleanup.

Adoptionsgeschichte

The repository metadata recorded 731 stars and 91 forks, which is substantial for a single-provider token utility. The README documents multiple distribution paths: precompiled binaries for Darwin, Linux, and Windows; Homebrew; a Google Container Registry image; source builds with Go; and tagged container images.

Homebrew core packaged oauth2l with version 1.3.3 and the `oauth2l` executable in the 2026-07-01 formula JSON. The same formula recorded 1,500 installs over 365 days, showing broader package-manager use than the smaller Objective-C utilities in this batch.

Wie es verwendet wird

oauth2l's core commands map directly to shell auth workflows: `fetch` prints a bearer token, `header` formats it as an Authorization header, `curl` obtains a token and invokes curl, `info` prints token metadata, `test` validates a token via exit status, and `reset` clears the default `~/.oauth2l` cache.

The README's examples show why it remains useful even in environments with full Google SDKs installed: it can use existing gcloud sessions, explicit credential files, service-account JWTs, domain-wide delegation, and ambient GCE or GKE service-account credentials, then hand the resulting token to ordinary command-line tools.

Warum Paket-Nerds sich dafür interessieren

oauth2l is a classic glue package: small enough to install as a standalone executable, official enough to be trusted by Google API users, and practical enough to bridge heavyweight cloud authentication into scripts, tests, and ad hoc API calls.

Zeitleiste

  • 2016-03-31: the public GitHub repository was created.
  • 2022-07-19: v1.3.0 added the three-legged OAuth loopback flow and PKCE support.
  • 2025-04-02: v1.3.3 updated dependencies and the Go version to address vulnerability-scanner findings.
  • 2026-07-01: Homebrew core formula metadata listed stable version 1.3.3.

Related projects

  • oauth2l pairs naturally with curl, Google Cloud SDK credentials, Google Cloud Console credential files, and Google service accounts. Compared with oauth2c, it trades generic OAuth breadth for Google-specific credential discovery and token 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

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

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.

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.oauth2l

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
oauth2lExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

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-08-03
Manager-Version1.3.4
Manager aktualisiert2026-07-27
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:oauth2l
Version1.3.4
PaketmanagerHomebrew
Homepagehttps://github.com/google/oauth2l
Repositoryhttps://github.com/google/oauth2l
Zuletzt aktualisiert2026-07-27T23:46:49+02:00
Pulseupdated
Bottlenicht erfasst
Dienstkeiner deklariert

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

Nix95%

oauth2l

nix profile install nixpkgs#oauth2l
  • normalized package name match
  • Abgeglichen nach: Oauth2l
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/oa/oauth2l/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
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation