mrkeyoor.comAsk

calesthio/Crucixtested 03 Oct 2026commit 3db7068

Crucix review

Crucix merits a private evaluation if you want a broad OSINT watch screen and will verify its output.

  • 89 packages
12 sto install
    Dataevaluationupdated 25 Oct 2026
    +13stars / 7d

    Crucix is a self-hosted public-data and OSINT dashboard. Its README describes 27 feeds queried in parallel every 15 minutes, with maps, market data, news and optional LLM, Telegram and Discord integrations. Those capabilities are documented claims; our recorded run covered dependency installation and audit results, not dashboard operation.

    Verdict

    Crucix merits a private evaluation if you want a broad OSINT watch screen and will verify its output. Our October 3, 2026 run at commit 3db7068 established a successful 12-second dependency installation and six recorded npm audit advisories. It did not establish dashboard reliability or application exploitability. Review deployment access, source timestamps and location provenance before depending on its briefings.

    We ran it

    Lab card: what happened when we ran Crucix
    Lab card from our sandbox run
    Screenshot of Crucix (crucix.live)
    crucix.live
    Install✓ · 12s89 packages · 31 MB
    Buildn/ano build script
    Testsn/ano test script
    Known vulns60 critical · 4 high · 1 moderate · 1 low (npm audit)
    Repo93 files~10,202 lines of source · 3 MB · 1 CI workflows · Dockerfile · tests dir

    Answers from our run

    Does Crucix build from source?

    Dependencies installed in 12 seconds (89 packages), and the project has no separate build step. We cloned commit 3db7068 into a clean Debian container with 3 CPUs and no project-specific setup.

    Does Crucix have tests you can run?

    Not through a standard command: the project exposes no test script or target that our harness could run.

    Does Crucix have known vulnerabilities in its dependencies?

    npm audit flagged 6 known advisories in the dependency tree at the time of our run.

    Who should not use Crucix?

    Readers seeking an independently validated intelligence or trading system.

    What are the alternatives to Crucix?

    Grafana, Dashy. Crucix merits a private evaluation if you want a broad OSINT watch screen and will verify its output.

    Setup3/5Dependency installation succeeded in 12.147 seconds in our October 3, 2026 run at 3db7068; server startup, credentials and integrations were not tested.
    Docs3/5The README supplies setup, credential, configuration and troubleshooting instructions; runtime accuracy and completeness were not verified.
    Community2/5Contribution instructions and substantive issue discussion are visible, but maintainer response consistency and support capacity were not evaluated.
    Maturity2/5CI, deployment files and a tests directory were detected; build and test steps were skipped for missing scripts, and six dependency advisories remain unassessed for reachability.

    Discussed on

    1. hnA self-hosted intelligence terminal that watches the world for signals4 points

    Who it’s for

    OSINT hobbyists evaluating a private dashboard for discovering topics to investigate.
    Researchers who will check consequential information against its original source.
    Developers willing to inspect source adapters, freshness handling and deployment controls before relying on the output.

    Who it’s NOT for

    Readers seeking an independently validated intelligence or trading system.
    Operators planning a publicly reachable deployment without reviewing and enforcing authentication.
    Anyone who needs this review to establish current feed availability, geographic accuracy or alert reliability. Our run did not measure those behaviors.

    Setup reality

    In our recorded run on October 3, 2026, commit 3db7068817e0c815df353fa0f19657c85142789d completed dependency installation successfully in 12.147 seconds, rounded to 12 seconds in the summary. Dependency storage was recorded as 31 MB. The parser recorded 89 dependencies, while the npm output said it added 90 packages; those counts have not been reconciled.

    Build and test steps were skipped because no corresponding scripts were detected. A tests directory was detected, so this does not establish that the repository has no tests. npm audit recorded six advisories: four high, one moderate and one low, with zero critical. Audit coverage and application reachability are unknown.

    The README requires Node.js 22+, documents port 3117 and estimates an initial sweep of 30 to 60 seconds. It says 18+ sources need no authentication, while other feeds and optional integrations need credentials. We did not start the server or verify those claims.

    Installation succeeded; the dashboard remains unevaluated

    Crucix brings a wide range of public feeds into one documented interface. The decision for a prospective operator is whether that aggregation is useful enough to justify checking the sources, freshness and deployment controls yourself.

    The README describes 27 feeds queried in parallel every 15 minutes, with a globe, flat map, news ticker, market data and optional messaging and LLM features. We did not verify that all feeds currently respond or that the resulting briefings are accurate. Treat the dashboard as a way to find leads that need further checking.

    What our recorded run established

    Our stored run began on October 3, 2026 at 04:38:25.803 UTC against commit 3db7068817e0c815df353fa0f19657c85142789d. The recorded sandbox configuration was 3 CPUs, 8 GB of memory and image lab-node:22. The image label alone does not establish the actual runtime version.

    Dependency installation exited successfully after 12.147 seconds. The summary rounds that to 12 seconds and records 31 MB of dependency storage. Its parser count is 89 dependencies, but the captured npm output says it added 90 packages. We have not reconciled those counts, so neither is presented as an independently verified exhaustive inventory.

    The checkout metrics were 93 files, approximately 10,202 source lines and 3 MB. Detection found one CI workflow, a Dockerfile, a Compose file and a tests directory.

    Build and test steps were skipped because the detected package scripts included neither build nor test. Nothing in this record shows a failed build or failed test. It also does not support the claim that Crucix has no test suite: a tests directory exists, and we did not investigate how to run its contents.

    npm audit recorded six dependency advisories: four high, one moderate and one low, with zero critical. The record does not establish exhaustive audit coverage, affected execution paths or whether an advisory is exploitable through Crucix. Advisory count is a reason to inspect the dependency report, not a count of demonstrated application vulnerabilities.

    We did not start the server, check an installed executable, query feeds, render the dashboard, wait for a sweep, send alerts, call an LLM or connect a brokerage account. There is no measured dashboard workload or reliability result.

    What setup still requires

    The README requires Node.js 22+ and documents the dashboard at port 3117. It estimates 30 to 60 seconds for the first sweep; that is the project's estimate, not our timing. It says 18+ sources require no authentication and describes credentials for additional coverage, including FRED, NASA FIRMS and EIA.

    Optional integrations add configuration work beyond installing dependencies. For example, the README documents Telegram credentials and an optional discord.js dependency for the full Discord bot. Its portfolio command mentions an Alpaca connection, but the supplied documentation and our run do not establish trading execution behavior.

    A useful next step is to start a private instance without optional messaging, model or brokerage connections. Check source health and compare a small sample of displayed items with their original records before adding credentials or acting on alerts. This is an evaluation recommendation, not a procedure we completed.

    Separate historical reports from verified current behavior

    The supplied issue reports identify questions worth checking against the exact revision you deploy. They are not findings from our sandbox run.

    Issue 112 originally reported random offsets applied to news coordinates. A September 22, 2026 comment says the underlying bug was fixed through PR 145. That comment is evidence of a reported fix, but we did not inspect the PR or verify its inclusion in a deployment. The issue's open status alone cannot establish that the behavior remains present. Check the deployed code and location provenance before treating a news marker as an event location.

    For timestamps, distinguish publication time, collection time and briefing time. A timestamp generated with new Date().toISOString() establishes the current clock value at execution, not an article's publication time. The README also explicitly describes preserving the latest non-empty OpenSky snapshot when requests are throttled. A populated flight panel therefore needs a freshness check against its underlying snapshot; we did not measure how that fallback appears in the interface.

    Review access before exposing the service

    Issue 111 reports unauthenticated data, health, locale and event-stream endpoints. A September 22 comment disputes its separate SSE memory-leak allegation, pointing to disconnect cleanup and pruning after write errors. We therefore do not repeat the leak allegation as an established defect.

    The same comment treats authentication as a deployment trust-boundary decision for a single-operator service. Our run did not test endpoint access. Keep an evaluation on a trusted private interface, or enforce and verify access controls at your gateway before making it reachable by others. Do not assume the localhost address shown in setup documentation proves the server binds only to loopback.

    How to read the ratings

    These are editorial evidence ratings, not benchmark results. The scale is 1 for little supporting evidence or substantial unresolved concerns, 2 for partial support with major gaps, 3 for adequate documented support with important verification gaps, 4 for strong support with limited gaps and 5 for comprehensive support within the stated scope. Unknown adoption, compatibility and runtime behavior receive no assumed credit.

    Setup receives 3/5 because dependency installation succeeded, while startup and integrations remain untested. Documentation receives 3/5 for its setup instructions, credential tables, configuration reference and troubleshooting guidance. Community receives 2/5 because a contribution path and issue discussion are visible, but response consistency and support capacity were not evaluated. Maturity receives 2/5 because deployment files, CI and a tests directory were detected, while no build or test script was exercised and dependency advisories require investigation.

    Choose by the dashboard you need

    Grafana's README supports a different workflow: querying, visualizing and alerting on metrics from configured data sources. Choose it when you want to build that monitoring workflow yourself. Dashy's README describes a homepage for applications and services, including status indicators and dynamic widgets. Choose it when navigation and service status are the main job. Neither alternative was run in this evaluation.

    For Crucix, the next decision should follow a private startup check and a source-by-source inspection of the information you actually need. Successful dependency installation is enough to begin that evaluation; it does not complete it.

    Alternatives

    ProjectWhat it isPick it when
    Grafana gh↗A platform for querying, visualizing and alerting on metrics from configured data sources.Choose Grafana when you want to construct dashboards and alert rules around your own metrics and data-source queries.
    DashyA self-hosted homepage with links, service status indicators and dynamic widgets.Choose Dashy when your goal is a homepage for your applications and services, with status checks and widgets.

    What people are saying

    1. [github-trending] calesthio/Crucix

    Sources

    1. Crucix README
    2. Crucix repository facts
    3. Issue 111: unauthenticated endpoints
    4. Issue 112: randomized map coordinates
    5. Issue 113: historical flight fallback
    6. Issue 114: plaintext RSS feeds
    7. Issue 115: rewritten GDELT timestamps
    8. Issue 116: publication-centroid fallback

    More data reviews