Self nomination for prometric, an ergonomic library for defining and using Prometheus metrics with an attribute macro.
Example:
// The `scope` attribute is used to set the prefix for the metric names in this struct.
#[metrics(scope = "app")]
struct AppMetrics {
/// The total number of HTTP requests.
#[metric(rename = "http_requests_total", labels = ["method", "path"])]
http_requests: Counter,
}
// Build the metrics struct with static labels, which will initialize and register the metrics
// with the default registry. A custom registry can be used by passing it to the builder
// using `with_registry`.
let metrics =
AppMetrics::builder().with_label("host", "localhost").with_label("port", "8080").build();
// Metric fields each get an accessor method generated, which can be used to interact with the
// metric. The arguments to the accessor method are the labels for the metric.
metrics.http_requests("GET", "/").inc();
I would like to self-nominate Goku, an HTTP load testing application written in Rust.
Besides being able to run as a CLI, since version 2.0.0, Goku integrates with the Model Context Protocol (MCP) — which means you can now use Goku programmatically from an LLM agent or any other MCP-aware client.
Give it a try and let me know what you think! Thanks!!
I would like to nominate rafx for next week's crate of the week. It's an extensible rendering framework and one of the few alternatives to wgpu. It offers a low level graphics interface, like wgpu, but also a complete rendering pipeline for modern 3D graphics. Unfortunately the development of the crate has gone rather slow (or stopped completely?) and the attention from readers might give it another chance. Thanks.
I've been working on mdbook-lint, a markdown linter built for mdBook projects but works great on any markdown. It has 60+ rules including markdownlint-compatible checks, mdBook-specific stuff like validating {{#include}} paths and SUMMARY.md structure, and content quality rules that catch TODOs, placeholder text, inconsistent terminology, and bad link text. Supports auto-fix for many rules, has a --fix CLI flag, JSON/TOML/YAML config, and can run as an mdBook preprocessor so you catch issues during build. There's also a Zed extension and GitHub Action if that's your thing.
Self-nomination: maker_web - High-performance, zero-allocation HTTP server for microservices. The API is very simple, easy to understand, and provides maximum freedom. It also allows you to set custom limits on connections, requests, and responses without affecting performance. Well, in general I tried my best, I personally like it
I would like to nominate joerl - new actor model framework which implements Erlang/OTP model with all the neat features. heavily prop tested, have many examples, benchmark with comparison against actix.
I'd like to nominate logos. Its a Lexer generator meant to be a modern alternative to lex. Its been around for a long time, but just released v0.16.0 which fixed many, many long standing bugs (~50, some over 5 years old) and made its regex syntax compliant with the regex crate. Its been a favorite of mine and I am really excited about the bug fixes in particular!
I have spent a regrettable amount of time working on making a CLI tool to generate structured markdown like rustdoc html with clickable links for the types and functions. It was because I wanted it for my own use, as it was getting a bit problematic to switch between terminal and browser so often. So I wanted something that would allow me to have the same doc quality directly in my editor. It's definitely not a crate of the week level project, but some people may find it helpful, there are fully navigable markdown docs for my project and all of its dependencies in the generated_docs/ folder that you can check out directly in the github repo :'D It's also on crates.io
I'd like to nominate wgsl-bindgen. It's a binding generator for WGSL, the WebGPU shading language, to be used with wgpu. The author said it best:
wgsl_bindgen transforms your WGSL shader development workflow by automatically generating Rust types, constants, and boilerplate code that perfectly match your shaders. Powered by naga-oil, it integrates seamlessly into your build process to catch shader-related errors at compile time rather than runtime.
I've used it in my Newtonian particle system for rendering and compute. It saved me huge amounts of time and worked perfectly.
kameo is an asynchronous actor framework with clear, trait-based abstractions for actors and typed messages. It includes lifecycle hooks and supervision for fault handling, and supports both local and networked actor communication using the same model.
I would like to self-nominate rust-mcp-sdk, a high-performance, asynchronous Rust toolkit for building MCP servers and clients, It now supports the latest MCP protocol specification (2025-11-25).