Who should evaluate XCheck
Anyone who can reach XCheck can inspect retained tasks and change integration settings, according to its README. That access model is the first deployment decision for this IP-investigation workflow.
XCheck accepts manual lists and CSV, XLS, XLSX, ZIP, LOG, and JSONL inputs. The documented sequence validates addresses, removes duplicates, checks a whitelist service, excludes non-public addresses, and waits for an operator to start ThreatBook queries. It suits analysts who already use those integrations and want persisted processing steps.
The README describes checkpoints, failed-node diagnostics, server-side pagination, bounded dashboard summaries, and TXT or XLSX exports at processing stages. It calls a 200,000-row CSV the current acceptance baseline. That is a project claim, not a workload measured in our run.
What our recorded run establishes
Our recorded run took place on September 30, 2026, at commit c6c96619816ffce572a3ea4fe92724b23b6d3760. The recorded sandbox configuration was 3 CPUs, 8 GB of memory, and image ghcr.io/astral-sh/uv:python3.12-bookworm. The installation tail independently identifies Python 3.12.12.
The installation step exited successfully in 33.301 seconds. The record reports 66 dependencies and 117 MB of installation storage. The build step exited successfully in 3.725 seconds, but its retained output is empty. These step results do not establish that a Docker image was built, the application was started, or an installed application passed a health check.
The test command exited successfully in 63.144 seconds. The retained pytest output reports "106 passed in 50.44s"; the parser summary records 106 passed, 0 failed, 0 skipped, and 0 errors. The command duration and pytest's own duration measure different scopes. The repeated summary line is not another set of passing tests. Complete-log reconciliation was not performed, so exhaustive unique test coverage remains unverified.
Pip-audit recorded 2 advisories affecting 1 package. Neither the affected package nor advisory IDs, severities, or scanned-package count appears in the supplied record. The 66-dependency figure does not establish audit coverage. Investigate those findings before deployment; passing tests do not resolve them.
The checkout record contains 102 files, approximately 10,647 source lines, and 1 MB before installation, plus one CI workflow, a Dockerfile, a Compose file, and a tests directory. The overall harness duration was 108 seconds. No live ThreatBook result, whitelist-service result, 200,000-row workload, throughput measurement, or frontend-specific check is established by this record.
Deployment depends on the network boundary
The README documents Docker Engine with Docker Compose and a listener at 0.0.0.0:8086. It says version tags publish matching AMD64 images. It also documents pinning v0.1.0; this review's measured commit should not be treated as a test of the v0.1.0 release artifact.
The security guidance explicitly states that XCheck has no login or role system. Reachable users can inspect retained task data, change integration endpoints, and replace or clear the ThreatBook credential. Restrict the host firewall to trusted ranges. For internet access, the README requires authentication, authorization, TLS, and request protections in front of the service. Those are documented deployment requirements, not findings from a penetration test.
Settings saved through the interface live in the local database and override first-start environment values. The README says the saved ThreatBook key is not returned by the settings API or displayed in the interface, but the database and its backups remain sensitive.
Approval controls and retained data
The documented workflow requires an operator to start ThreatBook queries. Missing, invalid, or unknown whitelist conclusions do not bypass that step. Batch size, safe rate, daily budget, and retry limits are configurable. These controls provide a review point before outbound queries; no spending reduction was measured.
The bound data/ directory contains SQLite state and uploaded source files. Version 1 intentionally has no history-deletion feature. Decide whether that retention model fits your logs and investigation records before uploading them.
The README instructs operators to back up the complete directory before upgrades. Live backups must preserve WAL consistency; otherwise stop the container before copying xcheck.db, xcheck.db-wal, and xcheck.db-shm.
Alternatives depend on the job
IntelOwl documents enrichment for files and observables, including IPs, domains, URLs, and hashes, using analyzers and connectors. Consider it when the investigation needs multiple analysis sources and observable types.
MISP documents structured indicator storage, correlation, and sharing. Consider it when the main task is maintaining and exchanging threat intelligence. Neither comparison establishes migration compatibility or equivalent ThreatBook workflow behavior.
How to read the scores
These are editorial suitability ratings, not benchmark results. On this five-point scale, 1 means the supplied evidence is insufficient for a positive assessment, 2 means limited supporting evidence, 3 means a documented fit with material validation gaps, 4 requires broader corroboration, and 5 requires strong evidence across the assessed scope. A low evidence score does not prove poor product quality.
Setup earns 3 because Compose deployment is documented and local steps succeeded, while deployment and integrations remain unverified. Documentation earns 3 because the README explains workflow, configuration, backups, and access limits, but the full deployment instructions were not validated. Community earns 1 because one completed documentation issue cannot establish adoption or support responsiveness. Maturity earns 2 because checkpoints and persistence are documented, while operational validation is limited and access control and deletion require deployment decisions.
For a pilot, use representative sanitized input, verify both integration connections, check the health endpoint, investigate the recorded advisories in the environment you intend to deploy, and confirm that your access and retention policies fit the documented behavior.

