Sister projects from n24q02m (click to expand)
| Project | Tagline | Tag |
|---|---|---|
| better-semantic-release | Drop-in python-semantic-release fork with built-in release-safety guards (orp... | Tooling |
| claude-plugins | Claude Code plugin marketplace for the n24q02m MCP servers -- install web sea... | Marketplace |
| crg | Knowledge graph for token-efficient code reviews -- semantic search and call-... | MCP |
| IMAP/SMTP email for AI agents -- read, send, organize folders, and manage att... | MCP | |
| fastretrieval | Fast multi-model retrieval runtime: ONNX and GGUF embeddings, reranking, and ... | Tooling |
| hull | hull is the shared monorepo core for the wet, crg and mnemo self-hosted stack | MCP |
| jules-task-archiver | Chrome Extension for bulk operations on Jules tasks via batchexecute API -- a... | Tooling |
| mnemo | Persistent AI memory with hybrid search. Open, free, unlimited. | MCP |
| notion | Markdown-first Notion for AI agents -- pages, databases, blocks, and comments... | MCP |
| sillstone | Pure-Rust multimedia, hashing, and array suite | Tooling |
| skret | Secrets without the server. | CLI |
| tacet | A self-distilling neuro-symbolic cascade that amortises LLM cost across knowl... | Tooling |
| telegram | Telegram for AI agents -- messages, chats, media, and contacts across both bo... | MCP |
| tools-docs | Docs portal for the n24q02m open-source tool stack (skret, MCP plugins, hull,... | Tooling |
| wet | Open-source MCP server for AI agents: web search, content extraction, and lib... | MCP |
| workspace | Google Workspace MCP server (Docs/Drive/Calendar/Gmail/Sheets/Slides/Tasks/Ch... | MCP |
Pure-Rust, zero-dependency multimedia, hashing, and array computing suite.
Sillstone provides verified, zero-dependency implementations of hashing, codecs, audio/image processing, and tensor abstractions with bindings for Python, Node.js, Go, and Java.
- Zero third-party dependencies: The entire Rust core depends strictly on
std. - Single ABI definition: Cross-language interfaces are deterministically generated from machine-readable IDL.
- Formally verified & cross-checked: Implementations are validated against CAVP, RFC, and standard test vectors.
| Layer | Crate | Description |
|---|---|---|
| T0 Foundation | sillstone-buffer |
Contiguous memory, striding, dtype, and slice views |
| T1 Core | sillstone-math, sillstone-digest, sillstone-inflate, sillstone-unicode |
Arithmetic kernels, cryptographic/non-cryptographic digests, decompression, text algorithms |
| T2 Codecs | sillstone-png, sillstone-jpeg, sillstone-mp3, sillstone-flac, etc. |
Pure-Rust media decoders and encoders |
| T3 Domains | sillstone-image, sillstone-audio, sillstone-video, sillstone-text, sillstone-file |
Domain abstractions and perception pipelines |
| T4 Fingerprints | sillstone-cdc (chunking); perceptual hashing, MinHash and audio/video fingerprints live in sillstone-image, sillstone-text, sillstone-audio, sillstone-video |
Perceptual hashing (pHash, minhash, chromaprint) and chunking |
Every SDK binds the same Rust core through the sillstone-ffi C ABI:
pip install sillstone # Python (ctypes)
npm install sillstone # Node.js (native N-API)
go get github.com/n24q02m/sillstone/sdk/go/sillstone # Go (cgo)- Java:
io.github.n24q02m:sillstoneon Maven Central (JNI)
pip install sillstone resolves to a prebuilt wheel for linux-x64, linux-arm64, darwin-arm64, darwin-x64 and win32-x64. Those carry the Rust cdylib and need no toolchain.
Every release also publishes a source distribution. It carries the Rust crates the ctypes extension links and no binary — one library cannot serve five platforms — so installing it compiles the cdylib on the machine doing the install. That route therefore needs a Rust toolchain (cargo, https://rustup.rs); the workspace has no third-party dependencies, so the build itself needs no network:
pip install --no-binary sillstone sillstoneWithout a toolchain, force a wheel instead:
pip install --only-binary :all: sillstoneThe archive ships only what sillstone-ffi builds: the sillstone CLI crate and the IDL generator are published on their own and are not part of it. CI builds the archive and installs it from source on Linux on every change, so a broken source route fails the pipeline rather than a user's install.