Student in CS, big data and AI

I build the things I wanted to exist.

Most of what's on this page started as a tool for a server I run, a script to skip a chore, or an excuse to learn something new. Then it got finished, because I was the one using it. One of them now runs on about 700 Minecraft servers.

01 about

The short version.

I'm studying computer science, big data and AI, with maths and statistics on the side. School covers the theory. The projects on this page are where I actually learn: by building something, breaking it, and trying again.

I follow a project all the way through, from the first architecture sketch to the boring maintenance afterwards. Security gets a lot of my attention, mostly because I run servers and have learned the hard way what happens when you don't.

speaks
French, English, Spanish
focus
Full-stack, data, security
github
@Xyness
02 stack

What I work with.

  • Languages Python, TypeScript, Rust, Java, SQL, Bash
  • Backend FastAPI, Node.js, Next.js, REST APIs in Sentinel, GitPulse
  • Data & AI Pandas, scikit-learn, Spark, Kafka, statistics in Sentinel, XBans
  • Infrastructure Docker, Linux, Git, CI/CD, VPS and cloud in Sentinel, SysAudit
  • Security Application security, server auditing, attack surface mapping in Phantom, SysAudit
03 projects

What I've built.

Four I'd show first. Each one has a README that goes into the details.

Streaming anomaly detection on crypto trades: Kafka carries them, Spark turns them into per-minute features, an Isolation Forest flags what looks wrong. A simulator injects anomalies on purpose, so the detector gets measured rather than trusted.

CI runs the whole pipeline end to end

  • Kafka
  • Spark
  • Python
  • Java
  • Docker

Maps the attack surface of a host you're allowed to scan: open ports and what's behind them, DNS and subdomains, TLS and HTTP posture, files forgotten on a web root. The port scanner is its own Rust binary.

338 Python tests and 8 Rust tests, all offline

  • Rust
  • Python
  • asyncio
  • SQLite

A command-line security audit of the machine you're sitting at, on Linux, macOS or Windows. Out comes a score out of 100 and one self-contained HTML report, each finding with the commands that fix it.

394 tests, CI on Linux, macOS and Windows

  • Python
  • Typer
  • Jinja
  • OSV.dev

Type a GitHub username and the profile comes back as a constellation of repos, a clickable contribution heatmap, languages over the years and a Wrapped-style recap with its own URL. No login anywhere.

  • Next.js
  • TypeScript
  • D3
  • Tailwind
live

Minecraft plugins

Two claim plugins and a framework with its own addons, written in Java and running on real servers, some open source and some paid. The corner of programming I keep coming back to.

  • SimpleClaimSystem open source Chunk-based land protection: menus to claim, merge and sell territory, 30+ settings per claim, map integrations, an API for other plugins. 1.18+, Folia included. 100k+ downloads, about 700 servers, rated 4.9/5 on Spigot
  • SimpleClaimSystem 2 paid The rewrite, for servers that outgrew a single permission list: roles per claim, 130+ permissions, 70+ protection flags, rent, an exportable audit log.
  • XCore open source The framework the other X plugins sit on: three cache layers, cross-server sync over Redis, an addon loader, GUIs described in YAML, a multi-currency economy, a web dashboard.
  • XBans paid Bans, mutes, warns and jails, plus ban waves. A Bayesian chat classifier trained in five languages reads through obfuscation, and alt detection weighs eleven signals.
  • XAuctionHouse paid Fixed-price listings and live auctions in any currency XCore knows, with snipe protection, tiered bids, search and price history.
  • XLogin paid Online mode decided per player: premium accounts connect with their skin and no password, everyone else registers. TOTP two-factor, sessions shared across servers, one jar for Velocity, BungeeCord and XCore.
  • XAntiLag paid Prevention rather than cleanup: per-chunk caps, mob and item stackers, redstone clock detection, and a TPS monitor that steps up optimisation as the server degrades and back down as it recovers.

The rest is on GitHub

04 contact

Say hi.

Email is the easiest way to reach me. I read everything and reply to most of it: a project, a question, or just something you're working on.