Urgent.News

What's breaking now, across thousands of outlets.

Tech

SNEPPX-Alg: Project Structure, Current Status, and How to Contribute

A transparent look at the 522-commit C++ AI runtime Project Overview SNEPPX-Alg is an open-source (MIT) AI runtime written in C++ with Python bindings. Its primary differentiator is a 10-layer security model (S0 to S9) that includes memory encryption (S1), control-flow obfuscation (S2), and runtime monitoring (S4). Directory Layout (What goes where) kernel/: Core tensor operations, automatic…

Project Overview: SNEPPX-Alg is an open-source C++ AI runtime with Python bindings, written in C++ and featuring a 10-layer security model. It includes memory encryption, control-flow obfuscation, and runtime monitoring. The project is organized into several directories, including kernel, algorithms, drivers, security, and net for hardware abstraction, model implementations, hardware abstraction, security layers, and distributed training coordinator respectively.

Current Stability: The project has stable CPU backend and core tensor operations, along with Dilithium signing/verification and ONNX import (basic ops). Experimental features include CUDA/ROCm backends, ZeRO-1 distribution, Mamba-2 and Diffusion model stubs.

How to Contribute: The project is currently seeking help with Python bindings, specifically for the from_pretrained() API to support safetensors files. Additionally, optimization of the kernel/ops/matmul.cpp to implement blocked matrix multiplication (tiled) could improve CPU inference speed by approximately 40%. Documentation is also needed, with clear API documentation for the public functions in bindings/python/src/.

The maintainers review pull requests within 48 hours and tag issues with 'good-first-issue' and 'help-wanted' for easier onboarding. The repository is hosted at ammar49-cyber / sneppx-alg.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Dev Log: 2026-08-12 — a 96s suite that became 42s, a capability that wasn't a scope, and four steps to a passkey

Fifteen commits, three repos, and the bulk of it in one: a control plane that got an MCP surface, a much faster test suite, and a handful of things that turned out to be quietly wrong once I looked…

  • A 96-second suite was optimized to 41 seconds through fifteen commits and three repositories.
  • Redundant seeder calls were removed, and test impact analysis was improved with pcov over Xdebug.
  • Four steps were outlined to enable passkeys in the application.

More from Wednesday 12 August →