Upstream software project

grok

powerful pattern-matching and reacting tool

About grok

powerful pattern-matching and reacting tool

This project links 3 native package records across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

grok repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 3 package records. Catalog coverage diagram, not an application screenshot.grok: recorded package coverageDebian 12 (Bookworm)3 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
grok
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
debian-12
License expression
Not reported
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

powerful pattern-matching and reacting tool

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. Package grok

    bookworm (Debian 12 (Bookworm)) (misc): powerful pattern-matching and reacting tool

    1.20110708.1-7+b1: amd64 arm64

    Source: grok

  2. Package libgrok1

    bookworm (Debian 12 (Bookworm)) (libs): shared libraries for grok

    1.20110708.1-7+b1: amd64 arm64

    Source: grok

  3. Package libgrok-dev

    bookworm (Debian 12 (Bookworm)) (libdevel): development files for grok

    1.20110708.1-7+b1: amd64 arm64

    Source: grok

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.