pkg.soopen package index

brew / Rang 12100

irrtoolset mit Homebrew, MacPorts installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install irrtoolset

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install irrtoolset

MacPorts ports tree · net/irrtoolset/Portfile · Quelle: api.github.com

Überblick

Paketzusammenfassung

Tools to work with Internet routing policies

Befehle und Aliase

  • peval
  • rpslcheck
  • rtconfig

Verlauf

Projektgeschichte und Nutzung

IRRToolSet is a suite for working with Internet Routing Registry routing policies expressed in RPSL. It is a classic network-operator package: small command-line tools such as `peval`, `rpslcheck`, and `rtconfig` turn registry policy data into checks, evaluations, and router configuration.

Projektgeschichte

The GitHub README defines IRRToolSet as tools for Internet routing policies stored in IRRs using Routing Policy Specification Language, with the goal of helping engineers automate router configuration, analyze routing policy, and maintain policy data. The README also notes the project's long history and mixed copyright across several parties.

RIPE NCC's archived project page says the Internet Routing Registry ToolSet project moved to Internet Systems Consortium maintenance. The preserved NEWS file shows an even older RAToolSet/IRRToolSet lineage, including RPSL implementation in 4.0.0, full RPSL compliance in 4.4.0, JunOS support in 4.6.0, RPSLng and IPv6-related work in 4.8.x, a 5.0.0 reorganization that left rtconfig, peval, and rpslcheck, and a 5.1.0 semantic-versioning release line.

Adoptionsgeschichte

IRRToolSet belongs to the operational ecosystem around RADb, RIPE, and other IRR databases. The Merit-operated irr.net overview says the IRR emerged early in 1995 as providers prepared for the end of the NSFNET Backbone Service and the commercial Internet, and it points users to IRRToolSet on GitHub. That context explains why the package persists: network operators still need ways to query and transform IRR/RPSL policy data.

Homebrew and MacPorts packaging make IRRToolSet available outside router-vendor environments, especially for engineers who want `peval`, `rpslcheck`, or `rtconfig` on a workstation. The upstream README also names bgpq4 as a better-maintained alternative for users seeking a fast IRRDB client.

Wie es verwendet wird

`peval` evaluates policy expressions, `rpslcheck` checks RPSL objects, and `rtconfig` generates router configuration from IRR policy. APNIC documentation describes tools such as IRRToolSet as useful for suggesting CIDR aggregates, checking aut-num objects and routes, and performing RPSL syntax checks.

Warum Paket-Nerds sich dafür interessieren

IRRToolSet is significant because it packages a piece of Internet routing operations history. It encodes old but still recognizable assumptions about IRR data, Cisco and JunOS configuration generation, IPv4/IPv6 policy evolution, and RPSL/RPSLng syntax, making it both useful tooling and a fossil record of how operators automated BGP policy.

Zeitleiste

  • 1995: The global IRR effort emerged as providers prepared for the post-NSFNET commercial Internet.
  • IRRToolSet 4.0.0: RPSL support was implemented.
  • IRRToolSet 4.4.0: The NEWS file described the toolset as fully RPSL compliant.
  • IRRToolSet 4.6.0: JunOS support was added to RtConfig.
  • IRRToolSet 4.8.x: RPSLng and IPv6-related support was added and refined.
  • IRRToolSet 5.0.0: The package was substantially reorganized, leaving rtconfig, peval, and rpslcheck.
  • 2016: IRRToolSet 5.1.0 began a semantic-versioning release line.
  • 2019: GitHub releases list IRRToolSet 5.1.3.

Related projects

  • IRRToolSet is related to RADb, IRRd, RIPE Database tooling, RPSL, RPSLng, bgpq4, router configuration generators, and BGP policy operations.

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.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
pevalExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
rpslcheckExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
rtconfigExecutableindexiertes ExecutableAus 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-Version5.1.3
Manager aktualisiert
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:irrtoolset
Version5.1.3
PaketmanagerHomebrew
Homepagehttps://github.com/irrtoolset/irrtoolset
Repositoryhttps://github.com/irrtoolset/irrtoolset
Bottlenicht erfasst
Dienstkeiner deklariert

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

MacPorts95%

irrtoolset

sudo port install irrtoolset
  • normalized package name match
  • Abgeglichen nach: Irrtoolset
MacPorts ports tree · api.github.com · MacPorts ports tree: net/irrtoolset/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

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.

Verwendete Quellen

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