macOS
Homebrewverifiziert · 100%
brew install talismanlocal Homebrew formula metadata
MacPortsverifiziert · 94%
sudo port install talismanMacPorts ports tree · devel/talisman/Portfile · Quelle: api.github.com
brew / Rang 1311
talisman mit Homebrew, MacPorts, winget installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für talisman in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Windows
Windows Package Managerverifiziert · 92%
winget install --id Thoughtworks.Talisman -eWindows Package Manager source index · Thoughtworks.Talisman · Quelle: cdn.winget.microsoft.com
Überblick
Paketzusammenfassung
Tool to detect and prevent secrets from getting checked in
Projektlinks
Befehle und Aliase
- talisman
Verlauf
Projektgeschichte und Nutzung
Talisman is a Thoughtworks-maintained secret-scanning CLI and Git-hook tool. It became package-manager relevant because it packages a common DevSecOps guardrail as a local binary that can run before code leaves a developer workstation.
Projektgeschichte
The official repository was initialized on 2015-12-14 and the first observed release tag, v0.1.0, is dated 2016-04-19. Its README defines the project as a tool that scans Git changesets so likely secrets or sensitive information do not leave the developer's workstation.
Adoptionsgeschichte
Talisman is distributed as a standalone executable, as a repository Git hook, and as a global Git hook template. The official README documents Homebrew installation, release-page binaries, an install script, pre-commit integration, and Husky integration, which placed it in the same day-to-day tooling layer as linters and formatters.
Wie es verwendet wird
The standard usage is to install the `talisman` binary and invoke it from pre-commit or pre-push hooks. It checks outgoing changesets for patterns such as SSH keys, authorization tokens, and private keys; it can also run directly as a CLI utility for Git repository scanning.
Warum Paket-Nerds sich dafür interessieren
Package nerds care about Talisman because it is a classic local-policy binary: small enough to install with Homebrew, easy to pin in hook frameworks, and useful before centralized secret-scanning infrastructure ever sees a commit. Its documented auto-update behavior from v0.4.4 also reflects the tension between reproducible pinned tooling and security tools that want to stay current.
Zeitleiste
- 2015-12-14: First commits in the official Git repository.
- 2016-04-19: First observed release tag, v0.1.0.
- 2018-10-08: v0.3.1 appears in the tag history before the README-documented v0.4.4 auto-update behavior.
- 2025-05-02: v1.37.0 appears as the latest observed tag and Homebrew stable version.
Related projects
- Talisman is commonly used with Git hooks, pre-commit, and Husky. In package-manager culture it sits beside tools such as git-secrets and detect-secrets, though this record relies only on the official Talisman sources for claims.
Quellen
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.
Configuration files
Config paths the tool may read or write during local use.
- Unix
.talismanrc
Executables
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
talisman | Executable | indexiertes Executable | Aus 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.37.0
Manager aktualisiert2026-07-26
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
- OKEs wurden keine Aktualitätswarnungen generiert.
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | brew:talisman |
|---|---|
| Version | 1.37.0 |
| Paketmanager | Homebrew |
| Homepage | https://thoughtworks.github.io/talisman/ |
| Repository | https://github.com/thoughtworks/talisman |
| Zuletzt aktualisiert | 2026-07-26T00:50:32+02:00 |
| Pulse | updated |
| Bottle | nicht erfasst |
| Dienst | keiner deklariert |
Source-Datenbank-Treffer
Andere Paketmanager-Einträge
Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.
MacPorts95%
talisman
sudo port install talisman- normalized package name match
- Abgeglichen nach: Talisman
winget95%
Thoughtworks.Talisman
winget install --id Thoughtworks.Talisman -e- normalized package name match
- Abgeglichen nach: Talisman
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.
Combined YAML source
View the package source record on GitHub.
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