intel/hyperscan

High-performance regular expression matching library

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 9 minutes ago
Added to GitGenius on September 12th, 2026
Created on September 21st, 2015
Open Issues & Pull Requests: 201 (+0)
GitHub issues: Enabled
Number of forks: 815
Total Stargazers: 5,489 (+0)
Total Subscribers: 182 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.5 days
Mean response time: 57.1 days
90th percentile: 335.4 days
Tracked items: 15

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 15
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 947 days
Stale 30+ days: 13
Stale 90+ days: 12

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Hyperscan is a high-performance regular expression matching library that enables simultaneous matching of large numbers of regex patterns against data streams.

The library solves the problem of efficiently matching many regular expressions at once, which is computationally expensive with traditional regex engines. Hyperscan uses hybrid automata techniques to handle this workload, allowing it to match tens of thousands of patterns simultaneously. It follows the regular expression syntax of libpcre but operates as a standalone library with its own C API, making it compatible with existing regex knowledge while offering superior performance for bulk matching scenarios.

Hyperscan is typically deployed in deep packet inspection library stacks, making it well-suited for network security, threat detection, and content filtering applications where multiple pattern matching against streaming data is required. Organizations that need to evaluate large volumes of data against extensive pattern sets will benefit most from its design. The tool is appropriate for projects where regex matching performance is a bottleneck and where matching many patterns simultaneously is a core requirement.

The project maintains a clear separation between stable and development work, with the master branch holding only tested releases suitable for production use while active development proceeds on a separate develop branch. The team operates a public mailing list for community questions and discussion, accepts bug reports through both email and GitHub issues, and provides a direct contact channel for inquiries that should not be posted publicly. The project includes comprehensive developer documentation covering both library building and API usage.