# Installer threatcl avec Homebrew Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de threatcl pour les workflows d'agents IA. ## installation ```sh sudo av install brew:threatcl ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install threatcl ``` Preuve: local Homebrew formula metadata ## Faits du paquet - **Clé du paquet:** brew:threatcl - **Gestionnaire de paquets:** Homebrew - **Version:** 0.6.5 - **Résumé source:** Documenting your Threat Models with HCL - **Page d'accueil:** - **Dépôt:** - **Dernière mise à jour:** 2026-08-01T13:15:26Z - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - threatcl (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 0.6.5 ## Historique du projet et usages threatcl is a command-line tool and HCL-based specification for documenting threat models in text files. The official README says the project was formerly named hcltm and was renamed to threatcl. ### Historique du projet The project frames threat modeling as a DevOps and version-control workflow: its README argues for a simple text-file format, a CLI-driven user experience, and integration with VCS. It builds on HashiCorp Configuration Language and the README explicitly connects that choice to Terraform familiarity and machine-readable structure. ### Historique d'adoption The official documentation positions threatcl for several installation and automation paths: Homebrew, Go install, Docker, and GitHub Actions. The README also documents release provenance through SLSA and GitHub attestations, which fits the security-tooling audience that may want to verify downloaded binaries and container images. ### Modes d'utilisation Users write threat models in HCL, then use the CLI to validate, list, view, export, query, generate dashboards, render data-flow diagrams, parse Terraform output, or run a server. The optional `config.hcl` file can override default classifications, impact types, STRIDE elements, and dependency classifications. ### Pourquoi les passionnés de paquets s'y intéressent For package nerds, threatcl is notable because it turns a security documentation practice into a normal source-controlled artifact with a CLI, Homebrew install, container image, GitHub Action, release attestations, and HCL syntax familiar to infrastructure engineers. ### Chronologie - Project README: hcltm is renamed to threatcl. - Current README: documents Homebrew, Docker, GitHub Actions, SLSA attestations, HCL threat models, GraphQL queries, Terraform parsing, and optional config.hcl. - Current docs site: documents Homebrew, Go, Docker, and GitHub Actions getting-started flows. ### Related projects - Related projects and specifications include Terraform and HCL2, OWASP threat-modeling material, OpenThreatModel, go-dfd, GitHub Actions automation, and security-as-code workflows. ### Sources - - ## Notes de sécurité Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour threatcl. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable. ## 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: config.hcl ## Combined YAML source View the package source record on GitHub. [combined/threatcl.yml](https://github.com/mxcl/pkgdb/blob/main/combined/threatcl.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph