• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

chimera/H03-May-2022-3,6711,871

cmake/H13-Jan-2021-573462

doc/dev-reference/H13-Jan-2021-5,1483,917

examples/H03-May-2022-1,9611,313

include/boost-patched/graph/H13-Jan-2021-530340

src/H13-Jan-2021-187,603130,029

tools/H03-May-2022-14,0379,861

unit/H03-May-2022-60,89141,298

util/H03-May-2022-3,9682,606

.clang-formatH A D13-Jan-2021140 76

.gitignoreH A D13-Jan-20211.5 KiB10288

CHANGELOG.mdH A D13-Jan-202117.1 KiB337314

COPYINGH A D13-Jan-20211.4 KiB2721

LICENSEH A D13-Jan-20215.9 KiB11993

README.mdH A D13-Jan-20211.6 KiB4429

hs.defH A D13-Jan-2021939 4441

hs_runtime.defH A D13-Jan-2021783 3634

libhs.pc.inH A D13-Jan-2021333 1210

README.md

1# Hyperscan
2
3Hyperscan is a high-performance multiple regex matching library. It follows the
4regular expression syntax of the commonly-used libpcre library, but is a
5standalone library with its own C API.
6
7Hyperscan uses hybrid automata techniques to allow simultaneous matching of
8large numbers (up to tens of thousands) of regular expressions and for the
9matching of regular expressions across streams of data.
10
11Hyperscan is typically used in a DPI library stack.
12
13# Documentation
14
15Information on building the Hyperscan library and using its API is available in
16the [Developer Reference Guide](http://intel.github.io/hyperscan/dev-reference/).
17
18# License
19
20Hyperscan is licensed under the BSD License. See the LICENSE file in the
21project repository.
22
23# Versioning
24
25The `master` branch on Github will always contain the most recent release of
26Hyperscan. Each version released to `master` goes through QA and testing before
27it is released; if you're a user, rather than a developer, this is the version
28you should be using.
29
30Further development towards the next release takes place on the `develop`
31branch.
32
33# Get Involved
34
35The official homepage for Hyperscan is at [www.hyperscan.io](https://www.hyperscan.io).
36
37If you have questions or comments, we encourage you to [join the mailing
38list](https://lists.01.org/mailman/listinfo/hyperscan). Bugs can be filed by
39sending email to the list, or by creating an issue on Github.
40
41If you wish to contact the Hyperscan team at Intel directly, without posting
42publicly to the mailing list, send email to
43[hyperscan@intel.com](mailto:hyperscan@intel.com).
44