# detect-secrets を Homebrew, Nix でインストール detect-secrets のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。 ## インストール ```sh sudo av install brew:detect-secrets ``` 追加のインストールコマンド: ### macOS - Homebrew (100%): ```sh brew install detect-secrets ``` 証拠: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#detect-secrets ``` 証拠: nixpkgs package indexes: detect-secrets from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix ## パッケージ情報 - **パッケージキー:** brew:detect-secrets - **パッケージマネージャ:** Homebrew - **バージョン:** 1.5.0 - **ソース概要:** Enterprise friendly way of detecting and preventing secrets in code - **ホームページ:** - **リポジトリ:** - **最終更新:** 2026-05-20T12:50:03Z - **生成日時:** 2026-08-03T19:37:03+00:00 ## 実行可能ファイル - detect-secrets (エイリアス) - detect-secrets-hook (エイリアス) ## インストール挙動 - Bottle: 利用不可 ## バージョンと鮮度 - ページ生成日: 2026-08-03 - マネージャ版: 1.5.0 ## プロジェクトの歴史と使われ方 detect-secrets is Yelp's open-source command-line scanner for finding secrets in code and, more importantly, preventing newly introduced secrets from entering a repository. Its README describes the baseline workflow as a way to accept existing findings while blocking new ones. ### プロジェクトの歴史 The GitHub repository was created in December 2017, and the README presents the tool as enterprise-friendly secret detection. Its changelog shows continued 1.x releases through 2024, including new detectors for GitLab, Telegram, PyPI, OpenAI, and IP addresses, plus support for newer Python versions. ### 採用の歴史 detect-secrets was designed for large repositories where immediately removing every old secret-like value may be impractical. The baseline model helped it fit pre-commit hooks and CI workflows: teams generate .secrets.baseline, audit it, and then use detect-secrets-hook or scans to catch new findings. ### 使われ方 The standard package-manager workflow is to install the CLI, run detect-secrets scan into .secrets.baseline, and wire detect-secrets-hook into staged-file or tracked-file checks. The README also documents auditing the baseline and tuning detectors and filters for local policy. ### パッケージ好きにとっての重要性 Package nerds care about detect-secrets because it is a practical DevSecOps CLI with a persistent config artifact rather than a one-shot grep-like scanner. It sits alongside pre-commit, GitHub secret scanning, trufflehog-style tools, and policy-driven CI checks. ### タイムライン - 2017: GitHub repository created for Yelp/detect-secrets. - 2020: 0.14.x releases continued the pre-1.0 series. - 2022: 1.2.0 added CI and release-pipeline work plus new token detectors. - 2024: 1.5.0 added OS-agnostic baseline support and more modern token detectors. ### Related projects - The project is commonly used with pre-commit-style hooks, CI pipelines, and other secret-scanning tools that enforce repository hygiene. ### ソース - - - - ## セキュリティノート detect-secrets に一致するローカルシークレット処理マニフェストは見つかりませんでした。将来の対応で安定したパッケージ URL を使えるよう、Nucleus パッケージメタデータはここに公開されています。 ## 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: .secrets.baseline ## 他のパッケージマネージャ記録 - Nix - detect-secrets: normalized package name match | nixpkgs package indexes: detect-secrets from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix ## Combined YAML source View the package source record on GitHub. [combined/detect-secrets.yml](https://github.com/mxcl/pkgdb/blob/main/combined/detect-secrets.yml) ## ソース - 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