Project announcement

Repository split & versioning notice

SentinelX by Uzumaru  ·  Effective immediately

To avoid unnecessary confusion, SentinelX has been split into two separate repositories.

We would like to clarify that only SentinelX Kuroko is open source. The SentinelX project as a whole is not open source. The project is now organized as follows:

SentinelX Misaka

Data collection & network control

Responsible for data collection and network control, including raw data acquisition, traffic interception, website blocking, connection logging, and other related security functions.

Closed source — proprietary

SentinelX Kuroko

Log analysis algorithm

Contains the open-source log analysis algorithm used to analyze the collected network logs. Open-sourced up to v1.5 under the CC BY-NC 4.0 license. Contributions and follow-up improvements are welcome.

Open source — CC BY-NC 4.0

Proprietary vs. open source

This separation clearly distinguishes the proprietary components from the open-source algorithm. Only SentinelX Kuroko is open source, while SentinelX Misaka and the complete SentinelX system remain closed source.

Versioning

As part of this repository split, the previous version numbers are no longer applicable.

Previously, the project used a unified versioning scheme. Going forward, SentinelX Misaka and SentinelX Kuroko will maintain their own independent version histories, with both repositories starting from v1.0.0.

Please note that the version numbers of SentinelX Misaka and SentinelX Kuroko are independent and are not expected to remain synchronized, as each repository will follow its own development and release cycle.

The open-source algorithm

The SentinelX algorithm is open-sourced up to v1.5 under the CC BY-NC 4.0 license. We welcome further contributions and follow-up improvements.

Project-Uzumaru/SentinelX-Algorithm

A note on SentinelX Uiharu

SentinelX Uiharu — the real-time risk control engine that judges whether an inbound request is malicious, automated or replayed before your application sees it — is a separate proprietary component and is not affected by this split. It is versioned independently as well.