SO-CRATES
v4.3.0 open-sourceThe section your link pointed to isn't on SO-CRATES's page any more, so we've brought you to the top.
Web application for analyzing pcappcapA packet capture, recorded network packets that can be inspected later. Analysts use it to reconstruct communication and investigate protocol behavior or suspicious traffic., log, and binary files using Suricata, YARA, and Sigma rules with a single-page UI.
docker run -e ALLOWED_HOSTS='*.killercoda.com' so-crates AI_SUMMARIES_DIR=/opt/so-crates/summaries python3 socrates.py PLAYBOOKS_DIR=/opt/so-crates/playbooks python3 socrates.py curl -s http://localhost:8000/api/rules-info | python3 -m json.tool docker run -e ENABLE_ARP_LOGGING=1 ... so-crates:latest curl https://so-crates.example.com/api/aggregation-data?analysis_id=abc123 curl https://so-crates.example.com/api/sankey-data?analysis_id=abc123
Summary
SO-CRATES is an open-source standalone web application for analyzing pcap, log, and binary files. It is available under the MIT license and runs as a service via Docker or Podman. The tool is for security analysts who investigate network traffic and threat artifacts. Its documentation positions it alongside dedicated network analysis tools. The project has had four releases in the window we track, with the last release occurring 13 days ago.
Web application for analyzing pcap, log, and binary files using Suricata, YARA, and Sigma rules with a single-page UI.
How SO-CRATES helps
What is actually happening in this capture, across the alerts, DNS, TLS, and file activity it contains?
runs Suricata network analysis, YARA binary scanning, and Sigma log detection against the uploaded pcap, log, or binary and lays every alert, metadata record, transcript, and hexdump out in one browsing UI
Which domains in this traffic look like tunneling or DGA activity rather than normal lookups?
aggregates every DNS query by registrable domain and scores each one across signals like high-entropy subdomain prefixes, low-vowel-ratio domains, and abnormal subdomain fan-out
Which other events in this capture belong to the same flow as this alert?
uses a community ID computed on every analysis to pull every log entry and alert sharing that flow, across protocols, into one correlated view
Is this the same TLS client or server seen elsewhere, without decrypting anything?
computes JA3, JA3S, and JA4 fingerprints on every analysis and surfaces them as their own rows in the TLS event's detail panel
What does this alert or YARA match actually mean, and what should I do about it?
shows a plain-English AI summary of the rule alongside a playbook section with investigation guidance sourced from Security Onion's rule and playbook repositories
Are the detection rules this analysis ran against current?
the Rules modal shows each ruleset's rule count and last-updated timestamp, flagging any Suricata, YARA, or Sigma ruleset over 30 days stale or never updated
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Screenshots
From the release notes, newest first. Click one to see it full size.Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for SO-CRATES, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail SO-CRATES puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
12 entries
No entries match these filters.
- October 20261
- September 20262
- August 20264
- July 20263
- June 20262
Project health
Issue, contributor and maintainer activity in dougburks/so-crates, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 2 +2 vs prior 12 months
- Maintainers 1 +1 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 5% of issues opened, last 12 months
- Median time to close 4.1 days first maintainer reply 2 days
- Open backlog 2 of 42 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 2
- Contributors / month 1
- Commits / month 23
- Stars 588
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.