# Installer yconalyzer avec Homebrew Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de yconalyzer pour les workflows d'agents IA. ## installation ```sh sudo av install brew:yconalyzer ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install yconalyzer ``` Preuve: local Homebrew formula metadata ## Faits du paquet - **Clé du paquet:** brew:yconalyzer - **Gestionnaire de paquets:** Homebrew - **Version:** 1.0.4 - **Résumé source:** TCP traffic analyzer - **Page d'accueil:** - **Dernière mise à jour:** 2026-07-10T09:59:35-04:00 - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - yconalyzer (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 1.0.4 ## Historique du projet et usages Yconalyzer is a low-overhead libpcap-based TCP connection analyzer. It captures or reads pcap data for a selected TCP port and summarizes connection duration, retry behavior, volume, and throughput. ### Historique du projet Yconalyzer was published on SourceForge as TCP Traffic Analyzer by Subbu Subramaniam. Its file feed shows early public tarballs in April 2010, followed by 1.0.x source archives and changelogs through June 2010. The project manual explains the core design: capture only TCP control packets with SYN, FIN, or RST set, then use those comparatively small packet streams to infer connection-level performance. That made it a specialized monitoring tool rather than a full packet dissector. ### Historique d'adoption Yconalyzer appears to have had modest adoption. It is documented on SourceForge, has a FreeBSD ports entry, and is packaged by Homebrew, but the available source material points to a small utility with a narrow operator audience rather than a large active ecosystem. Its adoption niche is server-side traffic diagnosis where tcpdump-compatible pcap files are already part of the workflow and an operator wants connection distributions without running a heavier analyzer. ### Modes d'utilisation The manual describes three modes: capture mode with `-w`, analyze mode with `-r`, and live traffic analysis. The `-p` port option is mandatory, and users can add ordinary tcpdump/BPF filters to narrow the capture. Typical examples include capturing port 80 or port 25 control packets, analyzing tcpdump-created pcap files, bucketing connections by duration or byte volume, and piping raw output through shell scripts for cron-based monitoring or alerts. ### Pourquoi les passionnés de paquets s'y intéressent Yconalyzer matters as an example of a tiny operations tool whose packaging value is preservation. The upstream is quiet, but package managers keep a buildable command around for people who still want this exact pcap-to-connection-summary behavior. It also demonstrates a classic Unix packaging pattern: a small C network utility, libpcap as the real platform interface, text output for scripts, and compatibility with tcpdump files. ### Chronologie - 2010-04-23: The SourceForge file feed lists an early yconalyzer.tgz upload. - 2010-05-18: A yconalyzer 1.0.2 archive is published. - 2010-06-03: A yconalyzer 1.0.3 archive and changelog are published. - 2010-06-29: A yconalyzer 1.0.4 archive and changelog are published. - 2013-04-11: SourceForge records a later project update date. ### Related projects - Related projects and technologies include libpcap, tcpdump, Berkeley Packet Filter, Wireshark, tshark, netsniff-ng, Tranalyzer, and RFC 793 TCP tooling. ### Sources - - - - - - ## Notes de sécurité narrow executable package without higher-risk signals. - **Risque Geiger:** vert / faible - narrow executable package without higher-risk signals ## Combined YAML source View the package source record on GitHub. [combined/yconalyzer.yml](https://github.com/mxcl/pkgdb/blob/main/combined/yconalyzer.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph