# spiffe-helper mit Homebrew, Nix installieren

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

## Installation

```sh
sudo av install brew:spiffe-helper
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install spiffe-helper
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#spiffe-helper
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/sp/spiffe-helper/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:spiffe-helper
- **Paketmanager:** Homebrew
- **Version:** 0.11.0
- **Quellzusammenfassung:** Tool that can be used to retrieve and manage SVIDs on behalf of a workload
- **Homepage:** <https://github.com/spiffe/spiffe-helper>
- **Repository:** <https://github.com/spiffe/spiffe-helper>
- **Zuletzt aktualisiert:** 2026-07-26T04:03:44+02:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- spiffe-helper (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.11.0
## Projektgeschichte und Nutzung

SPIFFE Helper is a small command-line utility in the SPIFFE ecosystem for fetching and renewing SVID material from the SPIFFE Workload API on behalf of another process.

### Projektgeschichte

The public GitHub repository was created in October 2017. Its README describes the tool as a helper that fetches X.509 SVID certificates, launches or signals a process that uses them, and refreshes certificates before expiry.

### Adoptionsgeschichte

Its package-manager footprint is niche but practical: the input records Homebrew and Nix packages, matching the kind of operator tool that appears in Unix package sets once workload identity moves from platform design into day-to-day deployment.

### Wie es verwendet wird

Typical use is `spiffe-helper -config <config_file>`, with `helper.conf` as the documented default. The README documents daemon and one-shot modes, file output under a configured certificate directory, and integration patterns where a supervisor such as systemd owns the real service.

### Warum Paket-Nerds sich dafür interessieren

Package maintainers care about SPIFFE Helper because it turns SPIFFE/SPIRE workload identity into ordinary files and signals: a familiar Unix packaging surface for certificates, keys, bundles, and reload hooks.

### Zeitleiste

- 2017: Public GitHub repository created.
- 2025: v0.10.0 added health-server related changes in the release notes.
- 2025: v0.11.0 release notes include a new `-version` flag.

### Related projects

- SPIFFE
- SPIRE
- go-spiffe
- systemd
- ghostunnel

### Quellen

- <https://api.github.com/repos/spiffe/spiffe-helper>
- <https://github.com/spiffe/spiffe-helper>
- <https://github.com/spiffe/spiffe-helper/releases>
- input source_facts.package-manager


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## 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

- Unix: helper.conf

## Credential files

- Unix: certs/svid.pem, certs/svid_key.pem, certs/svid_bundle.pem, certs/jwt_svid.token, certs/bundle.json
## Andere Paketmanager-Einträge

- Nix - spiffe-helper: normalized package name match | nixpkgs package indexes: pkgs/by-name/sp/spiffe-helper/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/spiffe-helper.yml](https://github.com/mxcl/pkgdb/blob/main/combined/spiffe-helper.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph