<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sh Raj</title>
    <description>The latest articles on DEV Community by Sh Raj (@sh20raj).</description>
    <link>https://dev.to/sh20raj</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F788719%2F0012e877-5660-4495-97b5-60a3d7f9121e.jpg</url>
      <title>DEV Community: Sh Raj</title>
      <link>https://dev.to/sh20raj</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sh20raj"/>
    <language>en</language>
    <item>
      <title>Sherlock for Privacy Audits: Find Your Own Username Footprint Across 400+ Sites</title>
      <dc:creator>Sh Raj</dc:creator>
      <pubDate>Tue, 17 Nov 2026 10:59:55 +0000</pubDate>
      <link>https://dev.to/sh20raj/sherlock-for-privacy-audits-find-your-own-username-footprint-across-400-sites-3c3o</link>
      <guid>https://dev.to/sh20raj/sherlock-for-privacy-audits-find-your-own-username-footprint-across-400-sites-3c3o</guid>
      <description>&lt;h1&gt;
  
  
  Sherlock for Privacy Audits: Find Your Own Username Footprint Across 400+ Sites
&lt;/h1&gt;

&lt;p&gt;Most people reuse at least one username. That makes it easy to remember, but it also creates a public trail: an old forum account, a developer profile, a gaming handle, or a social account that you no longer use.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/sherlock-project/sherlock" rel="noopener noreferrer"&gt;Sherlock&lt;/a&gt; is an open-source Python command-line tool that checks whether a username appears on public social networks and websites. Used responsibly, it can help you audit your own digital footprint before an old profile becomes an unexpected privacy problem.&lt;/p&gt;

&lt;p&gt;Sherlock is not a new project. Its GitHub repository dates back to December 2018. The monthly GitHub Trending snapshot collected at 06:57 UTC on November 17 showed 19,079 stars over the preceding 30 days, while the repository API showed 113,490 total stars at 10:51 UTC. The latest tagged release is v0.16.2, published on September 8, 2026, and the latest commit returned by the repository API was from November 1. This is renewed attention around a long-established tool, not a brand-new release.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn13auhjyjnhrtxnxn1bu.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn13auhjyjnhrtxnxn1bu.png" alt="Sherlock official demo screenshot" width="800" height="894"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Official Sherlock demo image from the &lt;a href="https://github.com/sherlock-project/sherlock/tree/master/docs/images" rel="noopener noreferrer"&gt;project documentation&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What Sherlock checks
&lt;/h2&gt;

&lt;p&gt;Sherlock takes one or more usernames and tests them against a maintained list of public websites. The current project documentation describes coverage of more than 400 social networks.&lt;/p&gt;

&lt;p&gt;It is a username-presence checker, not an identity-verification system. A result means that a website responded in a way Sherlock interprets as a possible account match. It does not prove that the account belongs to the person you have in mind.&lt;/p&gt;

&lt;p&gt;That distinction is essential for privacy work. Common handles can belong to unrelated people. Websites change their profile routes, block automated requests, or return ambiguous pages. A match should be checked manually before you draw conclusions.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe6a58szr23g868r87l6n.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe6a58szr23g868r87l6n.png" alt="Sherlock username search screenshot from the official documentation" width="800" height="200"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Official username-search visual from the Sherlock repository. Use results only for accounts you own or have permission to audit.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Install it with pipx
&lt;/h2&gt;

&lt;p&gt;The project recommends pipx as one installation option. It keeps the command-line application isolated from your system Python packages.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pipx install sherlock-project
sherlock --version
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The project metadata declares Python 3.9 or newer. The documentation also lists pip, uv, Docker, and several community-maintained packages as alternatives. Some third-party OS packages may lag behind the project, so use the official installation page if your distribution package fails.&lt;/p&gt;

&lt;h2&gt;
  
  
  Run a self-audit
&lt;/h2&gt;

&lt;p&gt;Use a username that you own or are explicitly authorised to check:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sherlock --print-found --csv --output ./my-own-handle.csv my-own-handle
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The command asks Sherlock to print found results and write a CSV report. The CLI also supports JSON and XLSX output, a per-site filter, a proxy, configurable timeouts, and a folder output option for multiple usernames.&lt;/p&gt;

&lt;p&gt;For a narrower check, the documented &lt;code&gt;--site&lt;/code&gt; option can limit the run to selected site names:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sherlock --site github my-own-handle
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Check the current &lt;code&gt;sherlock --help&lt;/code&gt; output before scripting around flags. The project has changed options over time, and automation should be pinned to a tested version.&lt;/p&gt;

&lt;h2&gt;
  
  
  Turn the results into a privacy checklist
&lt;/h2&gt;

&lt;p&gt;A useful audit does not end when the command exits. Review each possible match manually.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Confirm the account is yours.&lt;/strong&gt; Do not infer identity from a matching username alone.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check the profile's visibility.&lt;/strong&gt; Look for public email addresses, old biographies, location details, photos, and links to other accounts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review recovery and authentication settings.&lt;/strong&gt; Remove old recovery addresses and enable multi-factor authentication where the service supports it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Decide what to keep.&lt;/strong&gt; Delete unused accounts where possible, or remove identifying details and make the profile private.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Record the outcome.&lt;/strong&gt; Keep the CSV as a dated audit artifact, but store it securely because it may contain links to personal profiles.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The tool can help find places to inspect. It cannot delete accounts, determine whether a profile is truly yours, or tell you whether a site has copied your information elsewhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  Limitations and responsible use
&lt;/h2&gt;

&lt;p&gt;Sherlock relies on public website behavior. Its accuracy depends on site-specific checks that can become stale. A site may change its URL format, block requests, introduce login walls, or return a response that looks like a profile even when the username is unavailable.&lt;/p&gt;

&lt;p&gt;Expect false positives and false negatives. Re-run important checks manually in a browser. Avoid aggressive automation, respect each website's terms, and do not use the tool to stalk, harass, doxx, or compile dossiers on people without consent. This article's workflow is deliberately limited to your own public usernames or an authorised audit.&lt;/p&gt;

&lt;p&gt;Sherlock is MIT-licensed, but that does not grant permission to misuse the websites it checks. The privacy and legal rules of each service still apply.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sherlock or Maigret?
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/soxoj/maigret" rel="noopener noreferrer"&gt;Maigret&lt;/a&gt; is another open-source username OSINT tool. Both projects maintain site-specific checks, and both can be affected by changing website behavior.&lt;/p&gt;

&lt;p&gt;A practical choice is to compare the site lists, export formats, maintenance activity, and false-positive behavior for the services you care about. Neither tool should be treated as a definitive identity lookup service. For a small personal audit, Sherlock's simple CLI may be enough. For a larger investigation workflow, evaluate the alternatives in a controlled, consent-based environment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Watch a walkthrough
&lt;/h2&gt;

&lt;p&gt;This independent video demonstrates Sherlock's command-line workflow:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/-a0G4DvP0iM" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;It was published by All Things IT in December 2025, not by the Sherlock maintainers. Use it as a visual introduction and rely on the current official documentation for installation commands and supported options.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources and further reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/sherlock-project/sherlock" rel="noopener noreferrer"&gt;Sherlock GitHub repository&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://sherlockproject.xyz/installation" rel="noopener noreferrer"&gt;Official installation guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://sherlockproject.xyz/usage" rel="noopener noreferrer"&gt;Official usage guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://sherlockproject.xyz/sites" rel="noopener noreferrer"&gt;Current supported-sites list&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/sherlock-project/sherlock/releases/tag/v0.16.2" rel="noopener noreferrer"&gt;v0.16.2 release notes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/sherlock-project/sherlock/tree/master/docs/images" rel="noopener noreferrer"&gt;Sherlock documentation images&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/soxoj/maigret" rel="noopener noreferrer"&gt;Maigret alternative&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.youtube.com/watch?v=-a0G4DvP0iM" rel="noopener noreferrer"&gt;Independent Sherlock walkthrough&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Have you checked which old public profiles still use your primary username, and what would you remove first?&lt;/strong&gt;&lt;/p&gt;




&lt;p&gt;Written by &lt;a href="https://github.com/playlikeboy" rel="noopener noreferrer"&gt;Sh Raj&lt;/a&gt;. More engineering notes: &lt;a href="https://www.linkedin.com/in/sh20raj/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; · &lt;a href="https://youtube.com/@stackshade" rel="noopener noreferrer"&gt;StackShade on YouTube&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>python</category>
      <category>security</category>
      <category>privacy</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Inside X's For You Feed: Thunder, Phoenix, and the Recommendation Pipeline</title>
      <dc:creator>Sh Raj</dc:creator>
      <pubDate>Tue, 17 Nov 2026 10:59:19 +0000</pubDate>
      <link>https://dev.to/sh20raj/inside-xs-for-you-feed-thunder-phoenix-and-the-recommendation-pipeline-1jmm</link>
      <guid>https://dev.to/sh20raj/inside-xs-for-you-feed-thunder-phoenix-and-the-recommendation-pipeline-1jmm</guid>
      <description>&lt;h1&gt;
  
  
  Inside X's For You Feed: Thunder, Phoenix, and the Recommendation Pipeline
&lt;/h1&gt;

&lt;p&gt;A recommendation feed is not a single ranking model. It is a pipeline that has to find candidate posts, understand the viewer's history, remove content that should not appear, score the remaining candidates, and assemble a useful timeline within a request budget.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://github.com/xai-org/x-algorithm" rel="noopener noreferrer"&gt;xAI open-source repository&lt;/a&gt; makes a substantial part of the code behind X's For You feed inspectable. It is a valuable systems-design resource because it exposes the separation between retrieval, ranking, visibility filtering, and final feed blending.&lt;/p&gt;

&lt;p&gt;The repository is not new: GitHub records its creation on January 19, 2026. It appeared at position 3 in the Rust daily Trending snapshot collected at 06:57 UTC on November 17, with 159 stars shown for that day. Its latest commit in the repository API was made at 03:20 UTC today, with the message "Open-source X Recommendation Algorithm". GitHub showed 34,271 stars at 10:51 UTC. This is renewed attention around an actively updated codebase, not a newly created project.&lt;/p&gt;

&lt;h2&gt;
  
  
  The feed starts with retrieval, not ranking
&lt;/h2&gt;

&lt;p&gt;The README describes two main candidate sources.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Thunder&lt;/strong&gt; handles in-network retrieval. It keeps recent posts from accounts a viewer follows in memory.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Phoenix retrieval&lt;/strong&gt; and &lt;strong&gt;SimClusters&lt;/strong&gt; find out-of-network candidates. A popular-post source can add a shared set of recent posts.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Those sources are combined before the ranking model scores them. That distinction is important. A ranking model cannot select a relevant post that the retrieval stage never returned.&lt;/p&gt;

&lt;p&gt;The README also separates the post pipeline from the blending pipeline. The post pipeline finds, ranks, and filters posts. The blending pipeline adds other feed elements such as ads, Who to Follow recommendations, and prompts.&lt;/p&gt;

&lt;h3&gt;
  
  
  A simplified view
&lt;/h3&gt;

&lt;p&gt;The following is a conceptual diagram based on the repository README. It is not a complete production deployment diagram.&lt;br&gt;
&lt;/p&gt;

&lt;pre data-lang="mermaid"&gt;&lt;code&gt;flowchart TD
    A[Viewer request] --&amp;gt; B[Thunder: followed accounts]
    A --&amp;gt; C[Phoenix retrieval: out-of-network]
    A --&amp;gt; D[SimClusters and popular posts]
    B --&amp;gt; E[Candidate merge]
    C --&amp;gt; E
    D --&amp;gt; E
    E --&amp;gt; F[Phoenix ranking]
    F --&amp;gt; G[Visibility filtering and deduplication]
    G --&amp;gt; H[VMRanker diversity]
    H --&amp;gt; I[Feed blending]
    I --&amp;gt; J[For You timeline]&lt;/code&gt;&lt;/pre&gt;



&lt;p&gt;The source also makes clear that visibility filtering is a separate concern from ranking. Blocks, mutes, and content or account labels can determine whether a candidate is eligible to appear at all. A high model score should not override a visibility rule.&lt;/p&gt;

&lt;h2&gt;
  
  
  Phoenix uses two different model stages
&lt;/h2&gt;

&lt;p&gt;Phoenix contains both retrieval and ranking code.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Retrieval&lt;/strong&gt; uses a two-tower model. One tower encodes a viewer's recent engagement history. The other represents candidate posts. The system can compare embeddings to narrow a large corpus to a smaller candidate set.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ranking&lt;/strong&gt; uses a transformer to score the retrieved candidates. The model predicts the likelihood of different viewer actions, and those predictions are combined into a score. The README describes a Rust serving layer around the JAX model code.&lt;/p&gt;

&lt;p&gt;The repository also documents a VMRanker stage that applies a determinantal point process over candidate embeddings. In practical terms, this helps trade a little raw score for less similarity between neighboring posts. A feed with ten nearly identical high-scoring items is not necessarily a good feed.&lt;/p&gt;

&lt;p&gt;The current README records a notable October update: Phoenix retrieval was trained to surface posts people read through, and the ranking model was improved at estimating time spent. That is a useful reminder that recommendation systems can optimize for more than immediate clicks.&lt;/p&gt;

&lt;h2&gt;
  
  
  Explore the runnable Phoenix path
&lt;/h2&gt;

&lt;p&gt;The top-level repository contains more than a diagram. The Phoenix directory includes a quickstart that trains and serves small models with synthetic data.&lt;/p&gt;

&lt;p&gt;The documented requirements are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Linux with an NVIDIA GPU and CUDA 12&lt;/li&gt;
&lt;li&gt;Python 3.11 or newer and uv&lt;/li&gt;
&lt;li&gt;A Rust toolchain&lt;/li&gt;
&lt;li&gt;protoc 3.15 or newer&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;From the Phoenix directory, the quickstart begins with:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;uv sync --extra engine
&lt;span class="kd"&gt;export&lt;/span&gt; &lt;span class="nv"&gt;PYTHONPATH&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nv"&gt;$PWD&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then verify that the ranking serving path starts:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;uv run python xrex/inference/oss_bench/bench.py --smoke --service_type ranking
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This smoke test uses random weights. It verifies that the local serving stack can boot, not that a model has learned useful recommendations.&lt;/p&gt;

&lt;p&gt;The full quickstart goes further: it generates deterministic synthetic data, trains a small ranking model, saves and resumes checkpoints, serves the checkpoint through gRPC, and runs a retrieval-to-ranking request. The nano configurations are designed to make the path testable on a single GPU.&lt;/p&gt;

&lt;p&gt;That is a good way to learn the architecture without pretending you can reproduce X's production environment on a laptop.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is actually open, and what is missing?
&lt;/h2&gt;

&lt;p&gt;The Phoenix README says the repository includes production model definitions, training code, checkpointing, and the Rust serving engine. It also explains that internal data feeds, cluster orchestration, telemetry, and other xAI-specific infrastructure are not included. Synthetic generators replace production datasets in the local quickstart.&lt;/p&gt;

&lt;p&gt;That boundary matters. You can inspect real model code and run a proof-of-concept path, but you cannot reconstruct the exact production feed, its data, or every operational dependency from this repository alone.&lt;/p&gt;

&lt;p&gt;The code is licensed under Apache 2.0. There are no tagged GitHub releases in the repository's releases endpoint at the time of this run, so pin a commit when experimenting.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to use this repository as a developer
&lt;/h2&gt;

&lt;p&gt;It is most useful for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Learning how a large recommendation system separates retrieval from ranking.&lt;/li&gt;
&lt;li&gt;Studying two-tower retrieval and transformer-based candidate scoring.&lt;/li&gt;
&lt;li&gt;Understanding why visibility filtering is not the same thing as relevance ranking.&lt;/li&gt;
&lt;li&gt;Exploring a Rust serving layer connected to JAX model code.&lt;/li&gt;
&lt;li&gt;Building a small synthetic recommendation pipeline for experiments.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It is not a ready-made recommendation API for your own product. If you are building a new recommender, compare it with &lt;a href="https://www.tensorflow.org/recommenders" rel="noopener noreferrer"&gt;TensorFlow Recommenders&lt;/a&gt;, &lt;a href="https://pytorch.org/torchrec/" rel="noopener noreferrer"&gt;TorchRec&lt;/a&gt;, and &lt;a href="https://github.com/RUCAIBox/RecBole" rel="noopener noreferrer"&gt;RecBole&lt;/a&gt;. Those projects are general-purpose building blocks; none is a drop-in copy of X's feed.&lt;/p&gt;

&lt;p&gt;For a separate system-design walkthrough, this independent video covers the repository's major stages:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/rR-00bN2cmk" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;The video is from Debug with Dheeraj and was published in May 2026. It is not an official xAI presentation, so use the repository README and source files for current implementation details.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources and further reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/xai-org/x-algorithm" rel="noopener noreferrer"&gt;xAI x-algorithm repository&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/xai-org/x-algorithm#system-architecture" rel="noopener noreferrer"&gt;System architecture in the README&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/xai-org/x-algorithm/tree/main/phoenix" rel="noopener noreferrer"&gt;Phoenix architecture and model code&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/xai-org/x-algorithm/blob/main/phoenix/QUICKSTART.md" rel="noopener noreferrer"&gt;Phoenix local quickstart&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://help.x.com/en/resources/recommender-systems/for-you-home-timeline-recommendations" rel="noopener noreferrer"&gt;X's public explanation of For You recommendations&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.youtube.com/watch?v=rR-00bN2cmk" rel="noopener noreferrer"&gt;Independent architecture walkthrough&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;If you were designing a feed for a smaller community app, which stage would you build first: candidate retrieval, ranking, or visibility filtering?&lt;/strong&gt;&lt;/p&gt;




&lt;p&gt;Written by &lt;a href="https://github.com/playlikeboy" rel="noopener noreferrer"&gt;Sh Raj&lt;/a&gt;. More engineering notes: &lt;a href="https://www.linkedin.com/in/sh20raj/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; · &lt;a href="https://youtube.com/@stackshade" rel="noopener noreferrer"&gt;StackShade on YouTube&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>rust</category>
      <category>machinelearning</category>
      <category>systemdesign</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Lance v15 Beta: A Versioned Lakehouse Format for Multimodal Data</title>
      <dc:creator>Sh Raj</dc:creator>
      <pubDate>Tue, 17 Nov 2026 10:58:34 +0000</pubDate>
      <link>https://dev.to/sh20raj/lance-v15-beta-a-versioned-lakehouse-format-for-multimodal-data-45ma</link>
      <guid>https://dev.to/sh20raj/lance-v15-beta-a-versioned-lakehouse-format-for-multimodal-data-45ma</guid>
      <description>&lt;h1&gt;
  
  
  Lance v15 Beta: A Versioned Lakehouse Format for Multimodal Data
&lt;/h1&gt;

&lt;p&gt;Parquet is excellent at scanning columns. It is less convenient when an application needs to jump directly to individual records, retrieve image or video payloads, run vector search, and keep multiple versions of a changing training dataset.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/lance-format/lance" rel="noopener noreferrer"&gt;Lance&lt;/a&gt; is an open lakehouse format designed around those workloads. It combines a file format, table format, and catalog specification for datasets that may contain text, images, video, audio, embeddings, and ordinary structured columns.&lt;/p&gt;

&lt;p&gt;Lance is the format and SDK ecosystem. &lt;a href="https://lancedb.com/" rel="noopener noreferrer"&gt;LanceDB&lt;/a&gt; is a higher-level retrieval database built on it. The Lance repository is Apache-2.0 licensed; pin the SDK and the underlying file-format version separately because package and data compatibility are different concerns.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it is getting attention now
&lt;/h2&gt;

&lt;p&gt;Lance appeared at position 2 in the Rust daily GitHub Trending snapshot collected at 06:57 UTC on November 17, with 16 stars shown for that day. The repository's GitHub API record showed 7,348 stars at 10:48 UTC. This is an established project, created in 2022, rather than a brand-new repository.&lt;/p&gt;

&lt;p&gt;The immediate release signal is its active v15 beta line. Version &lt;strong&gt;v15.0.0-beta.25&lt;/strong&gt; was published at 05:36 UTC on November 17. This particular patch packages Lance protobuf definitions for downstream build scripts. That is a useful ecosystem improvement, but it is not a sweeping new storage feature. The beta release cadence is the stronger signal.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1ljj1ckbflllc4w0ouuw.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1ljj1ckbflllc4w0ouuw.png" alt="Lance file format overview from the official documentation" width="799" height="335"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;File-format overview from the &lt;a href="https://github.com/lance-format/lance/tree/main/docs/src/images" rel="noopener noreferrer"&gt;Lance documentation repository&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What the format provides
&lt;/h2&gt;

&lt;p&gt;Lance is designed for data that must be read in more than one way.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Random access:&lt;/strong&gt; retrieve individual rows and payloads without treating the dataset as a full sequential scan.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vector search:&lt;/strong&gt; perform exact nearest-neighbor search or use approximate nearest-neighbor indexes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hybrid retrieval:&lt;/strong&gt; combine vector similarity, full-text search, and SQL-style filtering.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Multimodal storage:&lt;/strong&gt; keep text, images, audio, video, and embeddings in one dataset model.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Data evolution:&lt;/strong&gt; add or evolve columns without rewriting every existing row.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Versioning:&lt;/strong&gt; use ACID transactions, time travel, tags, and branches to reason about dataset changes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Interoperability:&lt;/strong&gt; work through Arrow-based SDKs and integrations including Pandas, Polars, DuckDB, Spark, Ray, and PyArrow.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The project advertises up to 100 times faster random access than Parquet or Iceberg in its README. Treat that as a workload-specific project claim, not a universal benchmark. Test the operation your application actually performs.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqpl7s1ft1g78jhcqmpac.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqpl7s1ft1g78jhcqmpac.png" alt="Lance data evolution diagram from the official documentation" width="800" height="378"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The project documentation illustrates how Lance handles changes to dataset schemas and values.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  A small Python example
&lt;/h2&gt;

&lt;p&gt;The PyLance SDK is the lower-level way to create and inspect Lance datasets. The official quickstart uses Python with PyArrow.&lt;/p&gt;

&lt;p&gt;Create an isolated environment and install the documented dependencies:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;python -m venv .venv
&lt;span class="nb"&gt;source&lt;/span&gt; .venv/bin/activate
pip install pylance pandas pyarrow numpy tqdm
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now write a tiny Arrow table:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;lance&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;pyarrow&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;pa&lt;/span&gt;

&lt;span class="n"&gt;rows&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s2"&gt;"id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Alice"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"age"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;20&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s2"&gt;"id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Bob"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"age"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;30&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;]&lt;/span&gt;

&lt;span class="n"&gt;table&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;pa&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Table&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;from_pylist&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;rows&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;dataset&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;lance&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;write_dataset&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;table&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"./people.lance"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;dataset&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;count_rows&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The expected row count is 2. The important point is that the data is now stored as a Lance dataset, not as a Parquet file with a different extension.&lt;/p&gt;

&lt;p&gt;For vector search, define a fixed-dimension vector column and query it through the dataset API:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;results&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;dataset&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;to_table&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="n"&gt;columns&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"id"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"_distance"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;nearest&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="s2"&gt;"column"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"embedding"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"q"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;query_vector&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"k"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Here, &lt;code&gt;query_vector&lt;/code&gt; must have the same dimension and compatible type as the dataset's vector column. Lance supports exact nearest-neighbor scans without an index and approximate search with vector indexes. For a production retrieval path, create and tune the index rather than assuming a full scan will stay fast as the dataset grows.&lt;/p&gt;

&lt;h2&gt;
  
  
  Stable format versus the v15 beta
&lt;/h2&gt;

&lt;p&gt;The latest v15 package is a beta, so do not confuse the SDK release number with the underlying file-format version.&lt;/p&gt;

&lt;p&gt;Lance's versioning guide explains that the format version controls file compatibility. A newer format may offer better performance or compression, but an older reader may not understand it. The documentation specifically warns that unstable format versions, including the current 2.3 format and the &lt;code&gt;next&lt;/code&gt; alias, should be used for experimentation rather than production.&lt;/p&gt;

&lt;p&gt;For a production pipeline:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Pin the PyLance version in your dependency lockfile.&lt;/li&gt;
&lt;li&gt;Pin or explicitly choose a stable data-storage format version.&lt;/li&gt;
&lt;li&gt;Test readers and writers across the versions used by your jobs.&lt;/li&gt;
&lt;li&gt;Keep a rollback path before changing the format used for durable training data.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;To experiment with the current pre-release package, the repository documents:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pip install --pre --extra-index-url https://pypi.fury.io/lance-format pylance
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Do not silently mix beta writers with production readers. The exact v15.0.0-beta.25 release note is available in the &lt;a href="https://github.com/lance-format/lance/releases/tag/v15.0.0-beta.25" rel="noopener noreferrer"&gt;GitHub changelog&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lance, Parquet, Iceberg, Delta, or LanceDB?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Technology&lt;/th&gt;
&lt;th&gt;Strong fit&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Parquet&lt;/td&gt;
&lt;td&gt;Columnar interchange and scan-heavy analytics&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Apache Iceberg&lt;/td&gt;
&lt;td&gt;Open table management, snapshots, and multi-engine lakehouse workflows&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Delta Lake&lt;/td&gt;
&lt;td&gt;Transactional lakehouse tables and its Spark-centered ecosystem&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Lance&lt;/td&gt;
&lt;td&gt;Multimodal datasets, random access, vector indexing, and ML-oriented data workflows&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;LanceDB&lt;/td&gt;
&lt;td&gt;A higher-level vector and retrieval database built on Lance&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These tools overlap, but they are not the same abstraction. Lance can be a useful storage layer for ML datasets while an existing warehouse continues to serve analytical SQL. LanceDB is a better starting point if your immediate task is building an application-level retrieval database rather than managing the format directly.&lt;/p&gt;

&lt;h2&gt;
  
  
  A production use case worth watching
&lt;/h2&gt;

&lt;p&gt;The LanceDB channel published a November 16, 2026 talk titled &lt;strong&gt;From Raw Driving Logs to RL Training: A Petabyte-Scale Lance Pipeline in Production&lt;/strong&gt;. It describes how Applied Intuition uses versioned Lance datasets to curate multimodal driving logs, mine hard examples, and feed training dataloaders from the same tables.&lt;/p&gt;

&lt;p&gt;Training data changes as filters, labels, and edge cases change. Versioned datasets make those changes easier to track and reproduce.&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/f61j3f7JKw4" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;This is a talk hosted by the LanceDB channel, featuring an Applied Intuition engineer. It is a production case study, not a claim that every Lance workload has the same scale or performance.&lt;/p&gt;

&lt;h2&gt;
  
  
  When should you use it?
&lt;/h2&gt;

&lt;p&gt;Explore Lance if your data pipeline needs multimodal payloads, fast row access, vector search, or versioned ML datasets. Consider staying with Parquet or an existing table format if your workloads are primarily sequential scans and your current tools already solve the problem.&lt;/p&gt;

&lt;p&gt;The project is actively evolving, and the v15 line is beta. Pin versions, test compatibility, and keep experimental format versions away from production data until the compatibility guarantees are clear.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources and further reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/lance-format/lance" rel="noopener noreferrer"&gt;Lance GitHub repository&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://lance.org/quickstart/pylance/" rel="noopener noreferrer"&gt;PyLance getting started guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://lance.org/guide/read_and_write/" rel="noopener noreferrer"&gt;Read and write datasets&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://lance.org/guide/vector_search/" rel="noopener noreferrer"&gt;Vector search guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://lance.org/format/file/versioning/" rel="noopener noreferrer"&gt;Format versioning and compatibility&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/lance-format/lance/releases/tag/v15.0.0-beta.25" rel="noopener noreferrer"&gt;v15.0.0-beta.25 release notes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.youtube.com/watch?v=f61j3f7JKw4" rel="noopener noreferrer"&gt;Applied Intuition production pipeline talk&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Would you use Lance as the primary format for a multimodal training dataset, or keep Parquet and add a separate retrieval layer?&lt;/strong&gt;&lt;/p&gt;




&lt;p&gt;Written by &lt;a href="https://github.com/playlikeboy" rel="noopener noreferrer"&gt;Sh Raj&lt;/a&gt;. More engineering notes: &lt;a href="https://www.linkedin.com/in/sh20raj/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; · &lt;a href="https://youtube.com/@stackshade" rel="noopener noreferrer"&gt;StackShade on YouTube&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>dataengineering</category>
      <category>database</category>
      <category>python</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Arcane 3.0.1: A Self-Hosted Docker Control Plane With a Root-Level Warning</title>
      <dc:creator>Sh Raj</dc:creator>
      <pubDate>Tue, 17 Nov 2026 10:57:32 +0000</pubDate>
      <link>https://dev.to/sh20raj/arcane-301-a-self-hosted-docker-control-plane-with-a-root-level-warning-4imh</link>
      <guid>https://dev.to/sh20raj/arcane-301-a-self-hosted-docker-control-plane-with-a-root-level-warning-4imh</guid>
      <description>&lt;h1&gt;
  
  
  Arcane 3.0.1: A Self-Hosted Docker Control Plane With a Root-Level Warning
&lt;/h1&gt;

&lt;p&gt;Docker Compose is easy to understand when a project has one service. It becomes less pleasant when a server accumulates databases, workers, reverse proxies, backups, and several stacks that need updates. You can keep using the CLI, but the operational picture starts spreading across terminal sessions and folders.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/getarcaneapp/arcane" rel="noopener noreferrer"&gt;Arcane&lt;/a&gt; is a self-hosted web interface for managing that environment. Its recent v3 release makes it worth evaluating, especially if you want a visual control plane without moving your containers to a hosted service.&lt;/p&gt;

&lt;p&gt;There is one important warning before the screenshots: a tool with access to the Docker socket has serious host-level power. Arcane is convenient, but it must be deployed like privileged infrastructure.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Arcane does
&lt;/h2&gt;

&lt;p&gt;Arcane provides a web UI for Docker containers, Compose projects, images, volumes, backups, and update workflows. Its documentation also covers remote hosts and Swarm, Podman, user roles, passkeys, single sign-on, a mobile app, and an API.&lt;/p&gt;

&lt;p&gt;A project in Arcane is still a directory containing a Compose file and its related configuration. Arcane does not replace Compose. It gives you a place to inspect, edit, deploy, and monitor those projects. The source repository is BSD-3-Clause licensed. In a self-hosted deployment, your practical costs are infrastructure, storage, backups, and maintenance.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0i5kl2hnm1ll2f0ylcx6.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0i5kl2hnm1ll2f0ylcx6.jpg" alt="Arcane v3 dashboard in the light theme, from the official repository" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Official Arcane v3 dashboard screenshot. Source: &lt;a href="https://github.com/getarcaneapp/arcane/tree/main/.github/assets" rel="noopener noreferrer"&gt;Arcane repository assets&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The project appeared at position 6 in a GitHub daily Trending snapshot collected at 06:57 UTC on November 17, with 46 stars shown for that day. GitHub's repository API showed 9,015 stars at 10:47 UTC. The project had released v3.0.0 on November 14 and v3.0.1 on November 15. A recent r/homelab discussion comparing Dockge and Arcane also shows that people are evaluating it in the self-hosting community, although a discussion thread is not proof of broad adoption.&lt;/p&gt;

&lt;h2&gt;
  
  
  What changed in v3.0.1?
&lt;/h2&gt;

&lt;p&gt;The v3.0.1 release notes are more operational than flashy. They describe fixes for agent-mode startup and performance, stricter certificate and update verification, Docker disk-usage timeouts, Swarm behavior, Git-synced environment files, and backup startup.&lt;/p&gt;

&lt;p&gt;That is useful context for teams running multiple hosts. A management UI is only valuable if the agent and manager stay in sync and routine operations do not become a source of downtime.&lt;/p&gt;

&lt;p&gt;The v3 migration is not a casual image-tag change. The official migration guide says to upgrade a v2 installation to &lt;strong&gt;2.17.3 first&lt;/strong&gt;, start the manager and every agent once, back up the database and project files, then update the manager and agents together to v3.0. It also calls out renamed environment variables. Read the guide before changing an existing production installation.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxf0av3oti89jvt7j4urh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxf0av3oti89jvt7j4urh.png" alt="Arcane project logo from the official repository" width="500" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Project logo from the &lt;a href="https://github.com/getarcaneapp/arcane/tree/main/.github/assets" rel="noopener noreferrer"&gt;official Arcane assets&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Install a fresh instance
&lt;/h2&gt;

&lt;p&gt;The documented Docker Compose path requires Docker Engine and Docker Compose. First generate an encryption key:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker run --rm ghcr.io/getarcaneapp/manager:latest /app/arcane generate secret
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Copy the generated value. Create a &lt;code&gt;compose.yaml&lt;/code&gt; file:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;services&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;arcane&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;image&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;ghcr.io/getarcaneapp/manager:latest&lt;/span&gt;
    &lt;span class="na"&gt;container_name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;arcane&lt;/span&gt;
    &lt;span class="na"&gt;ports&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"3552:3552"&lt;/span&gt;
    &lt;span class="na"&gt;volumes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;/var/run/docker.sock:/var/run/docker.sock&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;arcane-data:/app/data&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;/opt/docker:/opt/docker&lt;/span&gt;
    &lt;span class="na"&gt;environment&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;ARCANE_APP_URL=http://localhost:3552&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;PUID=1000&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;PGID=1000&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;ARCANE_ENCRYPTION_KEY=replace-with-generated-key&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;ARCANE_PROJECTS_DIRECTORY=/opt/docker&lt;/span&gt;
    &lt;span class="na"&gt;cgroup&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;host&lt;/span&gt;
    &lt;span class="na"&gt;restart&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;unless-stopped&lt;/span&gt;

&lt;span class="na"&gt;volumes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;arcane-data&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Replace the encryption-key value. The official guide requires a passphrase of at least 32 characters. Change the URL if you will access Arcane from another device, and make sure the host projects directory is mounted at the same absolute path inside the container.&lt;/p&gt;

&lt;p&gt;Start it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker compose up -d
docker compose cp arcane:/app/data/initial-admin-password .
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The second command copies the generated initial admin password from the container. Use it for the first login and then set a new password.&lt;/p&gt;

&lt;p&gt;This gives you a local instance on port 3552. Before exposing it outside your machine, configure TLS, access controls, and a network boundary.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Docker socket is the real security decision
&lt;/h2&gt;

&lt;p&gt;The standard installation mounts:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/var/run/docker.sock:/var/run/docker.sock
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That socket gives Arcane access to the Docker API. The Arcane security documentation explicitly warns that creating containers can allow a user to mount the host filesystem or run a privileged container. In practical terms, someone who can control this Arcane instance may be able to take over the Docker host.&lt;/p&gt;

&lt;p&gt;A read-only mount of the socket file does not make Docker API requests read-only. A socket proxy can restrict which API routes are exposed, but it does not turn container creation into a harmless operation.&lt;/p&gt;

&lt;p&gt;Use Arcane only on a trusted host, keep its login and API keys private, restrict network access, and consider the documented socket-proxy setup. Do not treat the dashboard as a low-privilege convenience app.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it fits
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;Better fit&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Arcane&lt;/td&gt;
&lt;td&gt;Self-hosted management across Docker projects and remote hosts, with a modern UI&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Dockge&lt;/td&gt;
&lt;td&gt;A focused interface for managing Compose stacks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Portainer&lt;/td&gt;
&lt;td&gt;A broader container-management platform with a mature ecosystem and additional deployment options&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Docker CLI and Compose&lt;/td&gt;
&lt;td&gt;Minimal dependencies, explicit automation, and infrastructure-as-code workflows&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Arcane is attractive when you want to see containers and Compose projects together. It is less compelling if you already have a GitOps workflow that deliberately keeps production changes outside a web dashboard.&lt;/p&gt;

&lt;p&gt;A few features also deserve caution. The documentation marks container-to-Compose conversion as experimental. The separate CLI is described as early in development. Treat those features as optional until they have been tested against your own setup.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who should try it?
&lt;/h2&gt;

&lt;p&gt;Arcane is a reasonable candidate for homelab operators, small teams with a few Docker hosts, and developers who maintain several Compose-based services. It is not a replacement for Kubernetes orchestration, a backup strategy, or a secure deployment pipeline.&lt;/p&gt;

&lt;p&gt;For a new test instance, follow the official installation guide. For an existing v2 server, follow the migration guide in order. The official site also provides a demo, so you can inspect the interface before giving it access to a real Docker socket.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources and further reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/getarcaneapp/arcane" rel="noopener noreferrer"&gt;Arcane GitHub repository&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://getarcane.app/docs/get-started/installation" rel="noopener noreferrer"&gt;Official installation guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://getarcane.app/docs/get-started/migrate-v3" rel="noopener noreferrer"&gt;Migrate an existing installation to v3&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://getarcane.app/docs/security/socket-proxy" rel="noopener noreferrer"&gt;Docker socket proxy and security warning&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/getarcaneapp/arcane/releases/tag/v3.0.1" rel="noopener noreferrer"&gt;v3.0.1 release notes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://getarcane.app/" rel="noopener noreferrer"&gt;Arcane official demo&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.reddit.com/r/homelab/comments/1xx1otg/dockge_vs_arcane_for_container_management/" rel="noopener noreferrer"&gt;r/homelab Dockge vs Arcane discussion&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Would you trust a web dashboard with Docker socket access on your main server, or would you keep it isolated on a separate management host?&lt;/strong&gt;&lt;/p&gt;




&lt;p&gt;Written by &lt;a href="https://github.com/playlikeboy" rel="noopener noreferrer"&gt;Sh Raj&lt;/a&gt;. More engineering notes: &lt;a href="https://www.linkedin.com/in/sh20raj/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; · &lt;a href="https://youtube.com/@stackshade" rel="noopener noreferrer"&gt;StackShade on YouTube&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>docker</category>
      <category>devops</category>
      <category>opensource</category>
      <category>containers</category>
    </item>
    <item>
      <title>DeepSeek DeepInfer: Inside the Production Inference Engine for V4.1-Flash</title>
      <dc:creator>Sh Raj</dc:creator>
      <pubDate>Tue, 17 Nov 2026 10:56:43 +0000</pubDate>
      <link>https://dev.to/sh20raj/deepseek-deepinfer-inside-the-production-inference-engine-now-open-to-developers-29c1</link>
      <guid>https://dev.to/sh20raj/deepseek-deepinfer-inside-the-production-inference-engine-now-open-to-developers-29c1</guid>
      <description>&lt;h1&gt;
  
  
  DeepSeek DeepInfer: Inside the Production Inference Engine Now Open to Developers
&lt;/h1&gt;

&lt;p&gt;A model can look fast in a single-prompt demo and still struggle when dozens of requests compete for GPU memory, attention compute, and scheduling time. Production inference is a systems problem, not just a model-loading problem.&lt;/p&gt;

&lt;p&gt;That is the problem &lt;strong&gt;DeepInfer&lt;/strong&gt; is designed to address. DeepSeek describes it as the high-performance inference framework behind its large-scale production services. DeepSeek published its core inference code in October 2026, including an offline inference path and several of the scheduling and kernel optimizations used by its supported model.&lt;/p&gt;

&lt;p&gt;This is worth examining because it is not another universal chat UI or one-command local model runner. It is a specialised inference stack with demanding hardware and software requirements.&lt;/p&gt;

&lt;h2&gt;
  
  
  What DeepInfer actually is
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/deepseek-ai/DeepInfer" rel="noopener noreferrer"&gt;DeepInfer&lt;/a&gt; is an inference framework for &lt;strong&gt;DeepSeek-V4.1-Flash&lt;/strong&gt;. Its public repository contains model and sampler runtime code, optimized kernels, distributed execution paths, and examples for offline inference and benchmarking.&lt;/p&gt;

&lt;p&gt;The project was created on October 16, 2026. At 10:50 UTC on November 17, GitHub's repository API showed 26,147 stars. A Reddit discussion in &lt;a href="https://www.reddit.com/r/DeepSeek/comments/1xat1rk/deepinfer_is_out_hardware_requirements_and_whats/" rel="noopener noreferrer"&gt;r/DeepSeek on October 20&lt;/a&gt; reviews the hardware requirements and missing deployment components. It is an independent reality check, not an adoption metric. These signals show attention to a recent release, but they do not prove that the framework is easy to deploy or suitable for every model.&lt;/p&gt;

&lt;p&gt;The distinction matters: the repository is focused on one supported model family and a specific accelerator environment. Do not assume that a vLLM-compatible model or a consumer GPU will work just because the code is public.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fscc7mqd41v1lafv8npx8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fscc7mqd41v1lafv8npx8.png" alt="DeepInfer architecture overview from the official repository" width="800" height="422"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Project architecture visual, credited to the &lt;a href="https://github.com/deepseek-ai/DeepInfer" rel="noopener noreferrer"&gt;DeepInfer repository&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The engineering ideas worth understanding
&lt;/h2&gt;

&lt;p&gt;DeepInfer combines several optimizations rather than relying on one magic kernel.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Optimized kernels:&lt;/strong&gt; the project integrates FlashMLA, DeepGEMM, DeepEP, TileKernels, DeepSelect, and custom TileLang kernels.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Parallel execution:&lt;/strong&gt; its README documents attention data parallelism, balanced context parallelism, and mixture-of-experts expert parallelism with EPLB.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Speculative decoding:&lt;/strong&gt; DSpark and confidence-scheduled verification use draft tokens to reduce the work required for accepted output tokens. The &lt;code&gt;DEEPINFER_ENABLE_MTP_VARLEN&lt;/code&gt; and &lt;code&gt;DEEPINFER_USE_NEXTN_DECODE&lt;/code&gt; environment variables control parts of this path.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Scheduling:&lt;/strong&gt; an asynchronous batch scheduler overlaps CPU scheduling with device execution.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reproducibility:&lt;/strong&gt; batch-invariant inference and deterministic sampling are available on the documented NVIDIA path.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Structured output:&lt;/strong&gt; sampling parameters can constrain output using a regular expression, JSON schema, or EBNF grammar.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These features are useful in different ways. Speculative decoding targets token generation efficiency. Parallelism targets larger deployments. Batch invariance targets repeatability when request composition changes. Structured output is useful when a downstream service expects machine-readable responses rather than free-form text.&lt;/p&gt;

&lt;p&gt;The repository also publishes prefill and decode Pareto plots. Treat these as project-reported measurements, not independent benchmarks: the README describes prefill measurements on four SM100 GPUs and decode measurements on a larger 64-GPU setup. Your workload, hardware, context lengths, and batch sizes will change the result.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxudud5jpj5i6lo55g10n.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxudud5jpj5i6lo55g10n.png" alt="DeepSeek's published prefill throughput and latency curve" width="800" height="551"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Prefill benchmark visual from the project. Reproduce measurements on your own hardware before making capacity decisions.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Try the documented offline path
&lt;/h2&gt;

&lt;p&gt;This is a systems project, so check the prerequisites before cloning it.&lt;/p&gt;

&lt;p&gt;The current README lists:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Linux&lt;/li&gt;
&lt;li&gt;GCC 13 or newer&lt;/li&gt;
&lt;li&gt;Python 3.12&lt;/li&gt;
&lt;li&gt;CUDA 13 for NVIDIA, or CANN 9.2 for Huawei Ascend&lt;/li&gt;
&lt;li&gt;NVIDIA SM100 GPUs or Huawei Ascend 950 NPUs&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The public README does not list a general consumer-GPU fallback. If your machine does not meet these requirements, read the code and examples first rather than expecting a local run to succeed.&lt;/p&gt;

&lt;p&gt;For an NVIDIA build, the repository documents this flow from an empty Python 3.12 environment:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/deepseek-ai/DeepInfer.git
&lt;span class="nb"&gt;cd&lt;/span&gt; DeepInfer

&lt;span class="kd"&gt;export&lt;/span&gt; &lt;span class="nv"&gt;DEEPINFER_ACCELERATOR&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;nvidia
./build.sh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;examples/README.md&lt;/code&gt; then shows the offline inference command:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;python examples/offline_inference.py --ep 8
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The default checkpoint is &lt;code&gt;deepseek-ai/DeepSeek-V4.1-Flash-1017&lt;/code&gt;. The first run downloads it into the Hugging Face cache. If you already have a local Hugging Face model directory containing &lt;code&gt;config.json&lt;/code&gt; and safetensors, set &lt;code&gt;DEEPINFER_HF_MODEL_DIR&lt;/code&gt; to that path or pass the model directory through &lt;code&gt;--model_name&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;For example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="kd"&gt;export&lt;/span&gt; &lt;span class="nv"&gt;DEEPINFER_HF_MODEL_DIR&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;/models/DeepSeek-V4.1-Flash-1017
python examples/offline_inference.py --ep 8
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The repository's examples also expose &lt;code&gt;--dp&lt;/code&gt; and &lt;code&gt;--cp&lt;/code&gt; for different parallel configurations. Read the example documentation before changing those values; the topology must match the devices available to the process.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is not included
&lt;/h2&gt;

&lt;p&gt;This is the most important limitation to understand before planning a deployment.&lt;/p&gt;

&lt;p&gt;The project explicitly says that a complete inference service still needs components that are not included in this release:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A KV-cache system.&lt;/li&gt;
&lt;li&gt;Prefill/decode disaggregation.&lt;/li&gt;
&lt;li&gt;Load balancing across data-parallel replicas.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;DeepInfer therefore gives developers a substantial inference core, but it is not a complete managed serving platform. There are no tagged GitHub releases in the repository's releases endpoint at the time of this run, so users should pin a commit rather than assume a versioned release exists.&lt;/p&gt;

&lt;p&gt;The code is licensed under Apache 2.0. That does not automatically settle the licence or usage terms for the model checkpoint. Check the model card and weight terms separately before distributing a service.&lt;/p&gt;

&lt;h2&gt;
  
  
  DeepInfer, vLLM, SGLang, or TensorRT-LLM?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Choose&lt;/th&gt;
&lt;th&gt;When it makes sense&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;DeepInfer&lt;/td&gt;
&lt;td&gt;You are specifically evaluating DeepSeek-V4.1-Flash on the supported accelerator stack and want to inspect DeepSeek's inference implementation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;vLLM&lt;/td&gt;
&lt;td&gt;You need a broad serving ecosystem and support for many model families&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SGLang&lt;/td&gt;
&lt;td&gt;You want a serving framework with its own scheduling and structured-generation design&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;TensorRT-LLM&lt;/td&gt;
&lt;td&gt;Your deployment is NVIDIA-focused and you want to build around NVIDIA's inference stack&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These are not interchangeable drop-in replacements. Compare supported model architectures, hardware, quantization paths, batching behavior, and operational components before migrating.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who should explore it?
&lt;/h2&gt;

&lt;p&gt;DeepInfer is most relevant to inference engineers, infrastructure teams with supported accelerators, and researchers studying large-scale serving. It is also valuable as a code-reading exercise: the repository exposes how kernel selection, speculative decoding, expert parallelism, and scheduling fit together.&lt;/p&gt;

&lt;p&gt;It is not the right first choice for someone who wants to run a small model on a laptop or expose a generic OpenAI-compatible API in five minutes.&lt;/p&gt;

&lt;p&gt;For a short independent overview, see:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/HkBp4SjFqSU" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;The video is from Kiwi AI, not the DeepSeek maintainers. The source of truth for supported hardware and commands remains the official repository.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources and further reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/deepseek-ai/DeepInfer" rel="noopener noreferrer"&gt;DeepInfer repository and README&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/deepseek-ai/DeepInfer/tree/main/examples" rel="noopener noreferrer"&gt;Offline inference examples&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://huggingface.co/deepseek-ai/DeepSeek-V4.1-Flash-1017" rel="noopener noreferrer"&gt;DeepSeek-V4.1-Flash model card&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/deepseek-ai/DeepInfer/blob/main/doc/images/architecture_overview.png" rel="noopener noreferrer"&gt;DeepInfer architecture image&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.reddit.com/r/DeepSeek/comments/1xat1rk/deepinfer_is_out_hardware_requirements_and_whats/" rel="noopener noreferrer"&gt;Reddit discussion&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;What would you benchmark first in a production inference stack: prefill latency, decode throughput, or the scheduler under mixed request sizes?&lt;/strong&gt;&lt;/p&gt;




&lt;p&gt;Written by &lt;a href="https://github.com/playlikeboy" rel="noopener noreferrer"&gt;Sh Raj&lt;/a&gt;. More engineering notes: &lt;a href="https://www.linkedin.com/in/sh20raj/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; · &lt;a href="https://youtube.com/@stackshade" rel="noopener noreferrer"&gt;StackShade on YouTube&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>inference</category>
      <category>opensource</category>
      <category>python</category>
    </item>
    <item>
      <title>Lago: Build Usage-Based Billing for APIs and AI Products</title>
      <dc:creator>Sh Raj</dc:creator>
      <pubDate>Mon, 16 Nov 2026 10:42:54 +0000</pubDate>
      <link>https://dev.to/sh20raj/lago-build-usage-based-billing-for-apis-and-ai-products-4g0h</link>
      <guid>https://dev.to/sh20raj/lago-build-usage-based-billing-for-apis-and-ai-products-4g0h</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkpaopq66xibetb7lmlzo.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkpaopq66xibetb7lmlzo.png" alt="Lago billing platform overview" width="800" height="286"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Official product artwork from the &lt;a href="https://github.com/getlago/lago" rel="noopener noreferrer"&gt;Lago repository&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Usage-based pricing sounds simple until you have to implement it. You need to collect events, avoid double counting, aggregate usage over billing periods, apply price rules and credits, create invoices, and collect payment. Each step has edge cases that are easy to underestimate.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/getlago/lago" rel="noopener noreferrer"&gt;Lago&lt;/a&gt; is an open-source metering and usage-based billing platform. It is relevant to API products, SaaS platforms, compute services, and AI applications that charge for consumption rather than only a flat monthly subscription.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it is on the radar now
&lt;/h2&gt;

&lt;p&gt;In the GitHub Trending Go snapshot collected on &lt;strong&gt;November 16, 2026 at 06:57 UTC&lt;/strong&gt;, &lt;code&gt;getlago/lago&lt;/code&gt; appeared at position eleven, with 25 stars gained that day. That is modest movement, not a viral surge. Lago is an established project, so the useful distinction is that it is gaining fresh attention rather than being a brand-new repository.&lt;/p&gt;

&lt;p&gt;Its current README also puts a stronger emphasis on agent-facing interfaces: REST and OpenAPI, a CLI, an MCP server, and Agent SDKs for instrumenting model usage. The repository includes a maintained local demo that sends sample AI usage events, calculates charges, and checks that retrying a transaction does not double count it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Lago does
&lt;/h2&gt;

&lt;p&gt;Lago sits between product activity and revenue:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Usage events
    -&amp;gt; Metering
    -&amp;gt; Pricing and credits
    -&amp;gt; Entitlements
    -&amp;gt; Invoices
    -&amp;gt; Payments
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Your application reports usage. Lago turns those events into billable metrics, applies the pricing model, calculates what a customer owes, and creates invoices. A payment provider such as Stripe, Adyen, or GoCardless can handle the actual payment collection.&lt;/p&gt;

&lt;p&gt;This separation matters. A payment processor is not necessarily a complete usage-metering system, and a metering service is not necessarily a billing and invoicing engine.&lt;/p&gt;

&lt;p&gt;Lago supports usage such as API calls, seats, transactions, storage, GPU time, and model tokens. Pricing can combine recurring subscriptions, usage charges, allowances, credits, and overages. Its Direct model bills your own customers; its Embedded model lets a platform offer billing capabilities to its own customers.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvdypo1quyirnzxfmurhm.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvdypo1quyirnzxfmurhm.png" alt="Lago architecture diagram from the official README" width="800" height="409"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Official architecture illustration from the &lt;a href="https://github.com/getlago/lago" rel="noopener noreferrer"&gt;Lago README&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Try the maintained local demo
&lt;/h2&gt;

&lt;p&gt;The fastest way to understand the event-to-invoice flow is to run the repository's demo. It requires Docker, &lt;code&gt;curl&lt;/code&gt;, and &lt;code&gt;jq&lt;/code&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/getlago/lago.git
&lt;span class="nb"&gt;cd&lt;/span&gt; lago
./examples/agentic-ai-demo/run.sh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The script starts an isolated local Lago environment, seeds an example customer, metric, plan, and subscription, then sends illustrative input-token and output-token events. It checks the resulting usage and charge and retries a transaction to verify idempotency.&lt;/p&gt;

&lt;p&gt;Open &lt;code&gt;http://localhost:8080&lt;/code&gt; and sign in with the disposable credentials printed by the demo script. The demo is local; it does not access Lago Cloud. When you finish, remove its isolated services and data with:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;./examples/agentic-ai-demo/run.sh --cleanup
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That is a better first step than connecting a production billing account. You can inspect the customer, subscription, metric, events, and usage before deciding whether the model fits your product.&lt;/p&gt;

&lt;h2&gt;
  
  
  What an event looks like
&lt;/h2&gt;

&lt;p&gt;A basic usage event contains a unique transaction identifier, a customer identifier, a metric code, a timestamp, and optional properties.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="kd"&gt;export&lt;/span&gt; &lt;span class="nv"&gt;LAGO_URL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"http://localhost:3001"&lt;/span&gt;
&lt;span class="kd"&gt;export&lt;/span&gt; &lt;span class="nv"&gt;API_KEY&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"replace-with-the-api-key-printed-by-the-demo"&lt;/span&gt;

curl --request POST &lt;span class="s2"&gt;"$LAGO_URL/api/v1/events"&lt;/span&gt; \
  --header &lt;span class="s2"&gt;"Authorization: Bearer $API_KEY"&lt;/span&gt; \
  --header &lt;span class="s2"&gt;"Content-Type: application/json"&lt;/span&gt; \
  --data-raw &lt;span class="s1"&gt;'{
    "event": {
      "transaction_id": "request-0001",
      "external_customer_id": "customer-123",
      "timestamp": "2026-11-16T10:00:00Z",
      "code": "api_requests",
      "properties": {
        "endpoint": "/v1/search"
      }
    }
  }'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;code&lt;/code&gt; must match a billable metric you have configured, and the external customer must exist in Lago. Use a unique &lt;code&gt;transaction_id&lt;/code&gt; for each logical event. If your worker retries after a timeout, reuse the same transaction ID rather than creating a second billable event.&lt;/p&gt;

&lt;p&gt;A metric determines how usage is aggregated. For example, a &lt;code&gt;count_agg&lt;/code&gt; metric counts events, while sum and unique-count aggregations can use values inside &lt;code&gt;properties&lt;/code&gt;. Choose the aggregation based on what the customer is actually buying. Counting requests is not the same as charging for bytes transferred or tokens consumed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Agent tooling: useful, but privileged
&lt;/h2&gt;

&lt;p&gt;Lago's current developer workflow includes several interfaces:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The REST API and OpenAPI schema for application integrations.&lt;/li&gt;
&lt;li&gt;A CLI for inspecting billing data and automating terminal workflows.&lt;/li&gt;
&lt;li&gt;An MCP server that exposes supported billing operations to compatible agents.&lt;/li&gt;
&lt;li&gt;Python and JavaScript/TypeScript Agent SDKs for normalizing model usage and reporting token or cost events.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The important security detail is that the MCP server inherits the permissions of its Lago API key. A billing assistant with write access can change financial records. Use a scoped key, keep it out of prompts and source control, log tool calls, and require human confirmation for sensitive actions such as issuing credit notes or changing customer billing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Alternatives and trade-offs
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;Better fit&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Lago&lt;/td&gt;
&lt;td&gt;Open-source usage metering, pricing, credits, invoicing, and payment orchestration&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Stripe Billing&lt;/td&gt;
&lt;td&gt;A strong choice when Stripe is already central and the pricing model is relatively straightforward&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;OpenMeter&lt;/td&gt;
&lt;td&gt;Usage metering and event aggregation when you already own the billing and invoice layer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Orb or Chargebee&lt;/td&gt;
&lt;td&gt;Managed commercial billing workflows when operating billing infrastructure is not your goal&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The main Lago repository is &lt;strong&gt;AGPLv3&lt;/strong&gt; for self-hosted use. Its separate CLI, MCP server, and Agent SDK repositories use MIT licensing. Lago Cloud is commercial; self-hosting means your team operates the billing platform, database, queues, upgrades, and backups. Review the exact license and deployment terms for the components you use.&lt;/p&gt;

&lt;p&gt;Billing is a financial system, not just an API endpoint. You still need to test retries, event ordering, time zones, proration, taxes, credits, invoice corrections, and payment failures. Treat the local demo as a learning environment, not proof that a production integration is ready.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If your product charges for usage, what is the unit you would meter first: API calls, active seats, storage, compute time, or model tokens?&lt;/strong&gt; Define that metric before choosing the billing engine.&lt;/p&gt;

&lt;h3&gt;
  
  
  Sources and further reading
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/getlago/lago" rel="noopener noreferrer"&gt;Lago GitHub repository&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.getlago.com/docs" rel="noopener noreferrer"&gt;Official documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://githubtrending.today/language/go/" rel="noopener noreferrer"&gt;GitHub Trending Go snapshot&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.getlago.com/docs/guide/billable-metrics/aggregation-types/count" rel="noopener noreferrer"&gt;Count aggregation and event schema&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/getlago/lago/releases" rel="noopener noreferrer"&gt;Lago releases&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/getlago/lago/tree/main/examples/agentic-ai-demo" rel="noopener noreferrer"&gt;Maintained local AI billing demo&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/getlago/lago#deployment-options" rel="noopener noreferrer"&gt;Lago deployment and pricing overview&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Written by &lt;a href="https://github.com/playlikeboy" rel="noopener noreferrer"&gt;Shaswat Raj&lt;/a&gt; · &lt;a href="https://www.linkedin.com/in/sh20raj/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; · &lt;a href="https://youtube.com/@stackshade" rel="noopener noreferrer"&gt;StackShade on YouTube&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>billing</category>
      <category>opensource</category>
      <category>go</category>
      <category>saas</category>
    </item>
    <item>
      <title>Omnigraph: A Versioned Graph Database for Multi-Agent Context</title>
      <dc:creator>Sh Raj</dc:creator>
      <pubDate>Mon, 16 Nov 2026 10:42:15 +0000</pubDate>
      <link>https://dev.to/sh20raj/omnigraph-a-versioned-graph-database-for-multi-agent-context-f4p</link>
      <guid>https://dev.to/sh20raj/omnigraph-a-versioned-graph-database-for-multi-agent-context-f4p</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgaset1c4h0nzb45yha0l.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgaset1c4h0nzb45yha0l.jpg" alt="Omnigraph Studio showing a graph branch review" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Official Studio preview from the &lt;a href="https://github.com/ModernRelay/omnigraph" rel="noopener noreferrer"&gt;Omnigraph repository&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A normal database stores application records. A graph database makes relationships first-class. But systems used by teams of long-running agents need another property: one agent should be able to propose a change without silently overwriting another agent's work.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/ModernRelay/omnigraph" rel="noopener noreferrer"&gt;Omnigraph&lt;/a&gt; is a Rust graph database designed around typed domain models, hybrid retrieval, and versioned branches. It is an interesting project because it treats an agent's knowledge as durable, shared data that can be reviewed and merged like code.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it is trending now
&lt;/h2&gt;

&lt;p&gt;The GitHub Trending Rust snapshot collected on &lt;strong&gt;November 16, 2026 at 06:57 UTC&lt;/strong&gt; placed &lt;code&gt;ModernRelay/omnigraph&lt;/code&gt; at number one, with 174 stars gained that day. The repository describes itself as an object-storage-native graph database with branching and a typed ontology.&lt;/p&gt;

&lt;p&gt;The release history is active too. The latest stable release is &lt;strong&gt;v0.15.0&lt;/strong&gt;. The November 15 prerelease is &lt;strong&gt;v0.15.1-edge+6d92b43&lt;/strong&gt;, and it documents a storage-format difference from stable. That distinction matters more than the star count if you are evaluating it for production.&lt;/p&gt;

&lt;p&gt;This is a new and still-evolving database, not a mature replacement for every graph workload.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fapi.producthunt.com%2Fwidgets%2Fembed-image%2Fv1%2Ftop-post-badge.svg%3Fpost_id%3D1298575%26theme%3Dneutral%26period%3Ddaily" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fapi.producthunt.com%2Fwidgets%2Fembed-image%2Fv1%2Ftop-post-badge.svg%3Fpost_id%3D1298575%26theme%3Dneutral%26period%3Ddaily" alt="Omnigraph Product Hunt listing badge" width="250" height="54"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Launch-listing badge linked from the official project README; it is not a live adoption metric.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The core idea
&lt;/h2&gt;

&lt;p&gt;Omnigraph combines several capabilities in one runtime:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Typed ontology:&lt;/strong&gt; &lt;code&gt;.pg&lt;/code&gt; schema files declare node types, edge types, keys, and constraints. Writes are checked against the schema.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hybrid retrieval:&lt;/strong&gt; graph traversal, vector approximate-nearest-neighbor search, full-text search, and reciprocal-rank fusion can be combined.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Branching:&lt;/strong&gt; agents can write to a task-specific branch, inspect a diff, and merge the result after review.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Storage separation:&lt;/strong&gt; graph data uses the versioned Lance format and can live on local disk or supported S3-compatible object storage.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Policy enforcement:&lt;/strong&gt; Cedar policies are checked server-side on mutations, with authenticated actors and audit tracking.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The branch model is the most interesting design choice. Instead of giving every agent unrestricted write access to a shared graph, create a branch for an ingestion job or task. Review the diff, run checks, then merge. That gives the application a place to validate changes before they become shared knowledge.&lt;/p&gt;

&lt;h2&gt;
  
  
  Run a small local graph
&lt;/h2&gt;

&lt;p&gt;On macOS or Linux, the official installer downloads release binaries, verifies their SHA-256 checksum, and installs them under &lt;code&gt;~/.local/bin&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -fsSL https://raw.githubusercontent.com/ModernRelay/omnigraph/main/scripts/install.sh &lt;span class="o"&gt;|&lt;/span&gt; bash
&lt;span class="kd"&gt;export&lt;/span&gt; &lt;span class="nv"&gt;PATH&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"$HOME/.local/bin:$PATH"&lt;/span&gt;
omnigraph version
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Homebrew is also supported:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;brew tap ModernRelay/tap
brew install ModernRelay/tap/omnigraph
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Create a small schema. The example below stores claims and the sources that support them.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;node Source {
  slug: String @key
  title: String
}

node Claim {
  slug: String @key
  statement: String
}

edge Supports: Source -&amp;gt; Claim
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Create a query in &lt;code&gt;queries.gq&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;query sources_for_claim($claim: String) {
  match {
    $source: Source
    $c: Claim { slug: $claim }
    $source supports $c
  }
  return { $source.title as source }
  order { source asc }
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Lint the schema and query, then create a local graph:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;omnigraph lint --schema schema.pg --query queries.gq
omnigraph init --schema schema.pg graph.omni
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Put seed records in &lt;code&gt;seed.jsonl&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;{"type":"Claim","data":{"slug":"lower-latency","statement":"The migration reduced request latency."}}
{"type":"Source","data":{"slug":"load-test","title":"Load test report"}}
{"edge":"Supports","from":"load-test","to":"lower-latency"}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Load and query the graph:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;omnigraph load --data seed.jsonl --mode merge --target ./graph.omni

omnigraph query sources_for_claim --query queries.gq \
  --params &lt;span class="s1"&gt;'{"claim":"lower-latency"}'&lt;/span&gt; \
  --format table --target ./graph.omni
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;To make the review model concrete, load another file on a branch, inspect the diff, and merge only after the result is acceptable:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;omnigraph load --data more.jsonl --from main --branch review/first-change \
  --mode merge --target ./graph.omni

omnigraph branch diff review/first-change --into main --target ./graph.omni
omnigraph branch merge review/first-change --into main --target ./graph.omni
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is a deliberately small local workflow. The &lt;a href="https://github.com/ModernRelay/omnigraph/blob/main/skills/omnigraph/references/onboarding.md" rel="noopener noreferrer"&gt;onboarding guide&lt;/a&gt; explains how to evolve the schema, add data, and use branches.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it fits
&lt;/h2&gt;

&lt;p&gt;Omnigraph is worth evaluating for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A company knowledge graph that connects decisions, documents, people, and evidence.&lt;/li&gt;
&lt;li&gt;Agent memory where each task can create a branch and request review.&lt;/li&gt;
&lt;li&gt;A development graph linking issues, pull requests, dependencies, and releases.&lt;/li&gt;
&lt;li&gt;Research systems where claims need provenance and sources.&lt;/li&gt;
&lt;li&gt;A retrieval layer that needs relationships and vector or text search together.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The built-in agent skill is also notable. The CLI can export a version-matched skill for Claude Code, while the server exposes an MCP endpoint for agents that need to query or mutate a served graph. The skill and server should be kept in sync with the installed CLI.&lt;/p&gt;

&lt;h2&gt;
  
  
  Stable versus edge: read this before testing
&lt;/h2&gt;

&lt;p&gt;As of November 16, the latest stable release is v0.15.0. The November 15 edge build reports that it writes storage format 17, while v0.15.0 writes format 16 and serves only through format 16. A graph written by that edge build cannot be opened by v0.15.0.&lt;/p&gt;

&lt;p&gt;That is a concrete reason to keep experiments separate. Use a disposable graph or a backup when testing edge builds, and read the release compatibility table before pointing an edge binary at data that stable software must continue to read. Do not assume that a matching HTTP contract means matching on-disk compatibility.&lt;/p&gt;

&lt;p&gt;Omnigraph Cloud is in private preview. For a self-hosted cluster, you still need to plan authentication, storage, policies, backups, and upgrades. The local-file quick start is not the same thing as a multi-user production deployment.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it compares
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;Better fit&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Neo4j&lt;/td&gt;
&lt;td&gt;A mature graph platform with a broad ecosystem and established query workflows&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Kuzu&lt;/td&gt;
&lt;td&gt;Embedded graph queries inside an application or local data workflow&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PostgreSQL + pgvector&lt;/td&gt;
&lt;td&gt;Relational data with vector search when graph traversal is not central&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Omnigraph&lt;/td&gt;
&lt;td&gt;Typed, versioned graph state with branching and hybrid retrieval, especially for agent workflows&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The repository is MIT licensed. Its early release stage, changing storage formats, and private-preview cloud offering are real trade-offs. Start with a local graph and one concrete query before deciding whether its cluster model fits your deployment.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Would you let an agent write directly to a shared knowledge graph, or would you require every task to create a reviewable branch?&lt;/strong&gt; That decision is a good first test of whether Omnigraph's model matches your application.&lt;/p&gt;

&lt;h3&gt;
  
  
  Sources and further reading
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/ModernRelay/omnigraph" rel="noopener noreferrer"&gt;Omnigraph GitHub repository&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ModernRelay/omnigraph/tree/main/docs/user" rel="noopener noreferrer"&gt;Official user guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ModernRelay/omnigraph/blob/main/docs/user/install.md" rel="noopener noreferrer"&gt;Install guide and platform support&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ModernRelay/omnigraph/blob/main/skills/omnigraph/references/onboarding.md" rel="noopener noreferrer"&gt;Onboarding guide and local graph example&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ModernRelay/omnigraph/releases" rel="noopener noreferrer"&gt;v0.15.0 stable release and edge compatibility notes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.omnigraph.dev/studio" rel="noopener noreferrer"&gt;Omnigraph Studio&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://githubtrending.today/language/rust/" rel="noopener noreferrer"&gt;GitHub Trending Rust snapshot&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Written by &lt;a href="https://github.com/playlikeboy" rel="noopener noreferrer"&gt;Shaswat Raj&lt;/a&gt; · &lt;a href="https://www.linkedin.com/in/sh20raj/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; · &lt;a href="https://youtube.com/@stackshade" rel="noopener noreferrer"&gt;StackShade on YouTube&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>database</category>
      <category>rust</category>
      <category>ai</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Meta Astryx: A Customizable React Design System Built for Teams and AI Agents</title>
      <dc:creator>Sh Raj</dc:creator>
      <pubDate>Mon, 16 Nov 2026 10:41:32 +0000</pubDate>
      <link>https://dev.to/sh20raj/meta-astryx-a-customizable-react-design-system-built-for-teams-and-ai-agents-4e8h</link>
      <guid>https://dev.to/sh20raj/meta-astryx-a-customizable-react-design-system-built-for-teams-and-ai-agents-4e8h</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fncyx6h4n9b3opeept1zo.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fncyx6h4n9b3opeept1zo.png" alt="Astryx design system visual" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Official Astryx artwork from the &lt;a href="https://github.com/meta/astryx" rel="noopener noreferrer"&gt;Meta repository&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A design system is more than a collection of buttons. It is the shared set of components, tokens, interaction patterns, accessibility rules, and conventions that keeps a product consistent as its team grows.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/meta/astryx" rel="noopener noreferrer"&gt;Astryx&lt;/a&gt; is Meta's open-source React design system. It combines a component library, theming, templates, documentation, and a command-line interface. Its unusual angle is that the same structured documentation is intended for both developers and coding agents.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it is trending now
&lt;/h2&gt;

&lt;p&gt;The GitHub weekly trending snapshot collected on &lt;strong&gt;November 16, 2026 at 06:57 UTC&lt;/strong&gt; placed &lt;code&gt;meta/astryx&lt;/code&gt; at number one, with &lt;strong&gt;13,501 stars gained over the preceding seven days&lt;/strong&gt;. The weekly list is useful here because it measures sustained attention rather than a single burst.&lt;/p&gt;

&lt;p&gt;There is also concrete release activity. Astryx &lt;strong&gt;v0.7.16 was published on November 14&lt;/strong&gt;. Its notes include table row and column virtualization, infinite table loading, more explicit input-error behavior, and accessibility and focus fixes. On November 14, the Astryx team also announced that the design system was available in v0.&lt;/p&gt;

&lt;p&gt;Astryx is still in beta. The trending position is evidence of interest, not proof that every component is ready for every production workload.&lt;/p&gt;

&lt;h2&gt;
  
  
  What makes it different
&lt;/h2&gt;

&lt;p&gt;Astryx is built on React 19+ and StyleX. It ships precompiled CSS and typed React components, with more than 150 accessible components, ready-made themes, page templates, and a CLI.&lt;/p&gt;

&lt;p&gt;Its architecture has four useful layers:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Core components&lt;/strong&gt; provide common controls and layout primitives.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Themes&lt;/strong&gt; define colors, typography, spacing, radius, motion, and component-level variations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Templates&lt;/strong&gt; provide complete starting points for common pages such as dashboards, settings, and forms.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The CLI&lt;/strong&gt; exposes component documentation, templates, theme tools, and upgrade codemods.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The customization path is deliberately gradual. Start with a component as shipped, adjust theme tokens, add your own classes or CSS, and only then eject the component source with the &lt;code&gt;swizzle&lt;/code&gt; command if you need full ownership.&lt;/p&gt;

&lt;p&gt;That is a different trade-off from a copy-and-paste component collection. You keep a shared upstream package until you have a concrete reason to own a component.&lt;/p&gt;

&lt;h2&gt;
  
  
  Install it in a React application
&lt;/h2&gt;

&lt;p&gt;Astryx requires React 19 or later. The following pins the core packages to the current v0.7.16 release so that package versions stay aligned.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm install @astryxdesign/core@0.7.16 \
  @astryxdesign/theme-neutral@0.7.16 \
  @stylexjs/stylex

npm install -D @astryxdesign/cli@0.7.16
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For a Next.js App Router project, add the styles in the documented order:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="cm"&gt;/* src/app/globals.css */&lt;/span&gt;
&lt;span class="k"&gt;@import&lt;/span&gt; &lt;span class="s1"&gt;'@astryxdesign/core/reset.css'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;@import&lt;/span&gt; &lt;span class="s1"&gt;'@astryxdesign/core/astryx.css'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;@import&lt;/span&gt; &lt;span class="s1"&gt;'@astryxdesign/theme-neutral/theme.css'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then provide the theme:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="s1"&gt;'use client'&lt;/span&gt;

&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nc"&gt;Theme&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'@astryxdesign/core/theme'&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;neutralTheme&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'@astryxdesign/theme-neutral/built'&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nc"&gt;Providers&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;children&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;children&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;React&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;ReactNode&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Theme&lt;/span&gt; &lt;span class="n"&gt;theme&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="n"&gt;neutralTheme&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="n"&gt;children&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Theme&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And use a component:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nc"&gt;Button&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'@astryxdesign/core/Button'&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nc"&gt;Page&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Button&lt;/span&gt; &lt;span class="n"&gt;label&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"Hello Astryx"&lt;/span&gt; &lt;span class="n"&gt;variant&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"primary"&lt;/span&gt; &lt;span class="o"&gt;/&amp;gt;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The exact setup for Next.js, Vite, Tailwind, and CDN usage is in the &lt;a href="https://github.com/meta/astryx/blob/main/packages/core/README.md" rel="noopener noreferrer"&gt;core package README&lt;/a&gt;. If you use Next.js links, add the documented &lt;code&gt;LinkProvider&lt;/code&gt; with your router's Link component.&lt;/p&gt;

&lt;h2&gt;
  
  
  A useful CLI workflow for coding agents
&lt;/h2&gt;

&lt;p&gt;Install the CLI in the project and initialize its guidance:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx @astryxdesign/cli init
npx @astryxdesign/cli component Button
npx @astryxdesign/cli template dashboard
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The first command writes a component index into &lt;code&gt;AGENTS.md&lt;/code&gt; or &lt;code&gt;CLAUDE.md&lt;/code&gt;. The next command returns the component's API, variants, examples, and best practices. The template command emits a starting page.&lt;/p&gt;

&lt;p&gt;This is more useful than telling an agent to "use Astryx" and hoping it guesses the correct imports. The CLI provides the component inventory and the actual API reference that the project publishes.&lt;/p&gt;

&lt;h2&gt;
  
  
  When should you choose Astryx?
&lt;/h2&gt;

&lt;p&gt;Astryx makes sense when you want a cohesive component system, meaningful theming, and a maintained package rather than a folder of copied snippets. It may be especially useful for internal tools and dashboards, where forms, tables, navigation, and data-entry workflows dominate the interface.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;Main trade-off&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Astryx&lt;/td&gt;
&lt;td&gt;Full design system with themes, templates, CLI, and source customization; currently beta&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;shadcn/ui&lt;/td&gt;
&lt;td&gt;Components are copied into your codebase, giving direct ownership but making upstream updates your responsibility&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;MUI&lt;/td&gt;
&lt;td&gt;Mature component ecosystem and documentation, with a more recognizable default design language&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Radix UI&lt;/td&gt;
&lt;td&gt;Accessible low-level primitives when you want to build and own more of the visual system&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Astryx is MIT licensed, but its beta status matters. Pin versions, read migration notes, test the components you depend on, and avoid upgrading every package independently. The v0.7.16 release explicitly asks projects to align all &lt;code&gt;@astryxdesign/*&lt;/code&gt; packages to the same version.&lt;/p&gt;

&lt;p&gt;Meta says the internal system that preceded Astryx powered more than 13,000 apps. That is useful context about its origin, but it is a company-reported figure, not an independent performance benchmark for the newly open-sourced beta.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F62nbvq5s5hybqga8j23z.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F62nbvq5s5hybqga8j23z.png" alt="Astryx component and theme examples on its official site" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Official cover art for &lt;a href="https://astryx.atmeta.com/blog/how-astryx-works" rel="noopener noreferrer"&gt;How Astryx Works&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  See it in practice
&lt;/h2&gt;

&lt;p&gt;The Astryx team maintains a &lt;a href="https://astryx.atmeta.com/storybook/" rel="noopener noreferrer"&gt;Storybook&lt;/a&gt; and a &lt;a href="https://astryx.atmeta.com/blog/how-astryx-works" rel="noopener noreferrer"&gt;technical architecture article&lt;/a&gt;. An independent Better Stack walkthrough covers component selection, theme switching, token customization, and the agent-facing CLI:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/4GaR7k9VMp4" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Would you rather adopt a complete design system or keep a small set of primitives that your team owns?&lt;/strong&gt; Try the same dashboard in two Astryx themes and see whether the consistency is worth the dependency.&lt;/p&gt;

&lt;h3&gt;
  
  
  Sources and further reading
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/meta/astryx" rel="noopener noreferrer"&gt;Meta Astryx repository&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://astryx.atmeta.com/storybook/" rel="noopener noreferrer"&gt;Official documentation and Storybook&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/meta/astryx/releases/tag/v0.7.16" rel="noopener noreferrer"&gt;v0.7.16 release notes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://astryx.atmeta.com/blog/how-astryx-works" rel="noopener noreferrer"&gt;Astryx: How It Works&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://githubtrending.today/weekly/" rel="noopener noreferrer"&gt;GitHub weekly trending snapshot&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.youtube.com/watch?v=4GaR7k9VMp4" rel="noopener noreferrer"&gt;Independent Better Stack walkthrough&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Written by &lt;a href="https://github.com/playlikeboy" rel="noopener noreferrer"&gt;Shaswat Raj&lt;/a&gt; · &lt;a href="https://www.linkedin.com/in/sh20raj/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; · &lt;a href="https://youtube.com/@stackshade" rel="noopener noreferrer"&gt;StackShade on YouTube&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>react</category>
      <category>webdev</category>
      <category>designsystems</category>
      <category>opensource</category>
    </item>
    <item>
      <title>AG-UI Explained: A Protocol for Real-Time Agent Interfaces</title>
      <dc:creator>Sh Raj</dc:creator>
      <pubDate>Mon, 16 Nov 2026 10:40:59 +0000</pubDate>
      <link>https://dev.to/sh20raj/ag-ui-explained-a-protocol-for-real-time-agent-interfaces-3n17</link>
      <guid>https://dev.to/sh20raj/ag-ui-explained-a-protocol-for-real-time-agent-interfaces-3n17</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3l7e12tri6pttuqruvi2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3l7e12tri6pttuqruvi2.png" alt="AG-UI protocol project artwork" width="800" height="340"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Project visual from the &lt;a href="https://github.com/ag-ui-protocol/ag-ui" rel="noopener noreferrer"&gt;AG-UI repository&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A useful agent interface needs more than a stream of generated text. The user may need to approve a tool call, edit a form, see a chart update, interrupt a long-running task, or keep application state synchronized while the agent works.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://github.com/ag-ui-protocol/ag-ui" rel="noopener noreferrer"&gt;Agent–User Interaction protocol (AG-UI)&lt;/a&gt; defines a common event format for that connection. It sits between an agent backend and a user-facing application, so teams do not have to invent a different streaming contract for every framework.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it is trending now
&lt;/h2&gt;

&lt;p&gt;In the GitHub Trending TypeScript snapshot collected on &lt;strong&gt;November 16, 2026 at 06:57 UTC&lt;/strong&gt;, &lt;code&gt;ag-ui-protocol/ag-ui&lt;/code&gt; ranked second, with 355 stars gained that day. The project also published a release dated &lt;strong&gt;November 12&lt;/strong&gt;. That release included updates to the Claude Agent SDK and A2UI middleware, plus Python SDK fixes for tracing context and interrupted-run recovery.&lt;/p&gt;

&lt;p&gt;One migration detail is particularly important: the Claude SDK release removed &lt;code&gt;threadId&lt;/code&gt; and &lt;code&gt;runId&lt;/code&gt; from &lt;code&gt;TEXT_MESSAGE_*&lt;/code&gt; and &lt;code&gt;TOOL_CALL_*&lt;/code&gt; events. Consumers should read run identifiers from &lt;code&gt;RUN_STARTED&lt;/code&gt; or other run-level events instead. If you are already using the protocol, read the release notes before updating adapters.&lt;/p&gt;

&lt;p&gt;This is a real protocol adoption story, not a new model launch. The attraction is interoperability between frontends and agent frameworks.&lt;/p&gt;

&lt;h2&gt;
  
  
  What AG-UI standardizes
&lt;/h2&gt;

&lt;p&gt;AG-UI is an event-driven wire protocol. It standardizes the messages that move between an agent and the application around it. The protocol covers the lifecycle of a run, streamed text, tool calls and results, state snapshots and deltas, activity updates, and interruptions that require user input.&lt;/p&gt;

&lt;p&gt;A practical way to remember the ecosystem is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;MCP&lt;/strong&gt; connects an agent to tools and data.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A2A&lt;/strong&gt; connects agents to other agents.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AG-UI&lt;/strong&gt; connects an agent to the application and the person using it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These layers can work together. AG-UI does not replace your model provider, orchestration framework, database, or authorization system.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0imwziyxmgbsyy5uq2bt.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0imwziyxmgbsyy5uq2bt.png" alt="AG-UI protocol ecosystem diagram from the official repository" width="800" height="462"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Protocol visual from the &lt;a href="https://github.com/ag-ui-protocol/ag-ui" rel="noopener noreferrer"&gt;official repository&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick way to try it
&lt;/h2&gt;

&lt;p&gt;The official starter command creates an application scaffold:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx create-ag-ui-app my-agent-app
&lt;span class="nb"&gt;cd&lt;/span&gt; my-agent-app
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Follow the generated project's README to install its dependencies and start the development server. The scaffold is the fastest way to see the event flow before wiring in your own backend.&lt;/p&gt;

&lt;p&gt;For an existing application, the architecture has three pieces:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Frontend:&lt;/strong&gt; your React, Angular, mobile, or custom application. It renders events and exposes application context.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Runtime or adapter:&lt;/strong&gt; the server-side boundary that authenticates the user, forwards requests, and mediates tool calls.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Agent:&lt;/strong&gt; LangGraph, Mastra, Pydantic AI, Google ADK, CrewAI, or a custom implementation that emits AG-UI-compatible events.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The protocol is transport-agnostic. The implementation can use a streaming transport such as server-sent events or WebSockets, but the application should depend on the event contract rather than parsing arbitrary text fragments.&lt;/p&gt;

&lt;p&gt;A useful first exercise is to add one tool that returns structured data, stream its progress, and ask the user to confirm before applying a write. Keep the actual write operation in your backend. The frontend should not become the authority for permissions simply because it displays the approval button.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it helps
&lt;/h2&gt;

&lt;p&gt;AG-UI is useful when an agent is part of a product workflow rather than a separate chatbot:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A project-management app can show an agent creating tasks, then let a user edit the proposed task list.&lt;/li&gt;
&lt;li&gt;A support console can stream investigation steps and ask an operator to approve a refund or account change.&lt;/li&gt;
&lt;li&gt;A data product can render a chart or filter control from structured agent output.&lt;/li&gt;
&lt;li&gt;A mobile application can keep the same agent backend while using native controls on the device.&lt;/li&gt;
&lt;li&gt;A multi-agent workflow can show subagent activity without exposing every internal implementation detail.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The protocol is especially attractive when the backend framework may change. If your UI consumes a stable event contract, replacing one agent framework should not require rebuilding every frontend component.&lt;/p&gt;

&lt;h2&gt;
  
  
  Alternatives and trade-offs
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Approach&lt;/th&gt;
&lt;th&gt;Choose it when&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;AG-UI&lt;/td&gt;
&lt;td&gt;You need a shared event protocol between an agent and an interactive application&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Vercel AI SDK UI&lt;/td&gt;
&lt;td&gt;You want a cohesive SDK for streaming AI interactions in a supported web stack&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Custom SSE or WebSocket messages&lt;/td&gt;
&lt;td&gt;You have one small application and can own the protocol lifecycle&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;MCP&lt;/td&gt;
&lt;td&gt;You need an agent-to-tool interface, not the agent-to-user event stream&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;AG-UI does not supply authentication, authorization, rate limiting, durable run storage, or business rules. Those remain application responsibilities. An adapter can also expose only a subset of the protocol, so verify that your chosen framework supports the events your interface needs.&lt;/p&gt;

&lt;p&gt;The November 12 release is a reminder that event compatibility matters. Pin SDK versions, validate payloads against the published schema, and test recovery and replay behavior. In particular, do not assume every event carries identifiers that were present in an earlier release.&lt;/p&gt;

&lt;h2&gt;
  
  
  Watch a real integration
&lt;/h2&gt;

&lt;p&gt;The CopilotKit team also shared an &lt;a href="https://x.com/CopilotKit/status/2062534093309677662" rel="noopener noreferrer"&gt;AG-UI integration update on X&lt;/a&gt; while showing the Microsoft Agent Framework connection:&lt;/p&gt;

&lt;p&gt;&lt;iframe class="tweet-embed" id="tweet-2062534093309677662-769" src="https://platform.twitter.com/embed/Tweet.html?id=2062534093309677662"&gt;
&lt;/iframe&gt;

  // Detect dark theme
  var iframe = document.getElementById('tweet-2062534093309677662-769');
  if (document.body.className.includes('dark-theme')) {
    iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=2062534093309677662&amp;amp;theme=dark"
  }



&lt;/p&gt;

&lt;p&gt;CopilotKit maintains an &lt;a href="https://www.youtube.com/watch?v=bSn9EkOlXK8" rel="noopener noreferrer"&gt;AG-UI and Angular walkthrough&lt;/a&gt; showing how an agent connects to a frontend through the protocol. It is a useful companion to the &lt;a href="https://docs.ag-ui.com/" rel="noopener noreferrer"&gt;protocol documentation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/bSn9EkOlXK8" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If you already have an agent backend, what would be the first interactive action you would expose to users: an editable form, a tool approval, or a live data view?&lt;/strong&gt; Start with one action and keep its authorization on the server.&lt;/p&gt;

&lt;h3&gt;
  
  
  Sources and further reading
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/ag-ui-protocol/ag-ui" rel="noopener noreferrer"&gt;AG-UI GitHub repository&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ag-ui.com/" rel="noopener noreferrer"&gt;Official AG-UI documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ag-ui-protocol/ag-ui/releases/tag/release/2026-11-12" rel="noopener noreferrer"&gt;November 12, 2026 release notes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://githubtrending.today/language/typescript/" rel="noopener noreferrer"&gt;GitHub Trending TypeScript snapshot&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.copilotkit.ai/ag2/concepts/architecture" rel="noopener noreferrer"&gt;CopilotKit's AG-UI architecture guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.youtube.com/watch?v=bSn9EkOlXK8" rel="noopener noreferrer"&gt;CopilotKit Angular walkthrough&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Written by &lt;a href="https://github.com/playlikeboy" rel="noopener noreferrer"&gt;Shaswat Raj&lt;/a&gt; · &lt;a href="https://www.linkedin.com/in/sh20raj/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; · &lt;a href="https://youtube.com/@stackshade" rel="noopener noreferrer"&gt;StackShade on YouTube&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>protocols</category>
      <category>webdev</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Univer Office SDK: Embed Editable Spreadsheets and Docs in Your App</title>
      <dc:creator>Sh Raj</dc:creator>
      <pubDate>Mon, 16 Nov 2026 10:40:31 +0000</pubDate>
      <link>https://dev.to/sh20raj/univer-office-sdk-embed-editable-spreadsheets-and-docs-in-your-app-1k2i</link>
      <guid>https://dev.to/sh20raj/univer-office-sdk-embed-editable-spreadsheets-and-docs-in-your-app-1k2i</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7zeewbqp7frqpjo3xxz9.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7zeewbqp7frqpjo3xxz9.png" alt="Univer Office SDK showing an editable spreadsheet surface" width="800" height="267"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Official artwork from the &lt;a href="https://github.com/dream-num/univer" rel="noopener noreferrer"&gt;Univer repository&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;An editable spreadsheet is a surprisingly large product feature. Once users can change cells, you inherit formulas, selection, undo and redo, copy and paste, keyboard navigation, formatting, persistence, and file compatibility. Building all of that from scratch is rarely a good use of an application team's time.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/dream-num/univer" rel="noopener noreferrer"&gt;Univer&lt;/a&gt; is an open-source Office SDK that lets developers embed spreadsheet and document experiences into their own web products. It is worth watching because it is not just a static grid: its plugin architecture, application-facing APIs, and headless workflows make it possible to connect an editor to the rest of a product.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it is trending now
&lt;/h2&gt;

&lt;p&gt;In the GitHub Trending TypeScript snapshot collected on &lt;strong&gt;November 16, 2026 at 06:57 UTC&lt;/strong&gt;, &lt;code&gt;dream-num/univer&lt;/code&gt; appeared at position one with 988 stars gained that day. That is a dated snapshot, not a promise about tomorrow's ranking. The project also tagged &lt;strong&gt;v1.5.1 on November 16&lt;/strong&gt;. The preceding v1.5.0 release, published November 14, added dedicated chart sheets, stacked line charts, error bars, editable Board layout improvements, and formula-calculation memory improvements.&lt;/p&gt;

&lt;p&gt;The useful signal is the combination of a current trending position and a fresh release with concrete editor capabilities. This is an established project gaining attention, not a brand-new repository.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Univer actually provides
&lt;/h2&gt;

&lt;p&gt;Univer is best understood as an application framework for office-like editing surfaces. Its open-source foundation includes Sheets and Docs functionality, while the wider product family and commercial packages cover additional workflows.&lt;/p&gt;

&lt;p&gt;The architecture is modular:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Presets&lt;/strong&gt; assemble a useful set of plugins for a common editor configuration.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Plugins&lt;/strong&gt; provide capabilities such as rendering, formulas, sheets, documents, and UI.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Facade APIs&lt;/strong&gt; give application code a stable way to work with workbooks, worksheets, ranges, and commands.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Commands and undo data&lt;/strong&gt; let related features participate in one coherent edit history.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Headless usage&lt;/strong&gt; lets Node.js processes reuse content models and plugins without mounting the browser editor.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last point matters. A product can use the same workbook model for a visible editor, an automated import job, a report generator, or an assistant that updates a value after a user approves the change.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2k4spfvp4vmrv4a8xxv7.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2k4spfvp4vmrv4a8xxv7.webp" alt="Univer Sheets product preview from the official README" width="799" height="293"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Official Sheets preview from the &lt;a href="https://github.com/dream-num/univer" rel="noopener noreferrer"&gt;Univer README&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Build a first spreadsheet
&lt;/h2&gt;

&lt;p&gt;The current README quick start uses a bundler such as Vite and the Sheets Core preset. It requires a browser container with a height.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pnpm add @univerjs/presets @univerjs/preset-sheets-core
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Add the editor container:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;div&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"app"&lt;/span&gt; &lt;span class="na"&gt;style&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"height: 100vh"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/div&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then initialize the preset:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nc"&gt;UniverSheetsCorePreset&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'@univerjs/preset-sheets-core'&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;UniverPresetSheetsCoreEnUS&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'@univerjs/preset-sheets-core/locales/en-US'&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;createUniver&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;LocaleType&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;mergeLocales&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'@univerjs/presets'&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="s1"&gt;'@univerjs/preset-sheets-core/lib/index.css'&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;univerAPI&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;createUniver&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;locale&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;LocaleType&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="no"&gt;EN_US&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;locales&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nc"&gt;LocaleType&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="no"&gt;EN_US&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;mergeLocales&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;UniverPresetSheetsCoreEnUS&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;presets&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="nc"&gt;UniverSheetsCorePreset&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="n"&gt;container&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'app'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="n"&gt;univerAPI&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;createWorkbook&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This creates an editable spreadsheet using the open-source packages. The application-facing API can then populate a range, read calculated values, or save a workbook snapshot. The official README demonstrates a quotation sheet with quantity, unit price, and formula-driven totals. It also shows how to wait for the formula engine's lifecycle stage before making edits.&lt;/p&gt;

&lt;p&gt;Two implementation details are easy to miss:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Keep coordinated &lt;code&gt;@univerjs/*&lt;/code&gt; packages on the same version. Mixing release lines is a common source of dependency and runtime problems.&lt;/li&gt;
&lt;li&gt;In a React or Vue component, retain the instance returned by &lt;code&gt;createUniver&lt;/code&gt; and dispose it when the component unmounts. Do not initialize a new editor on every render.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The &lt;a href="https://docs.univer.ai/guides/sheets/getting-started/installation" rel="noopener noreferrer"&gt;installation guide&lt;/a&gt; and &lt;a href="https://docs.univer.ai/guides/sheets/getting-started/lifecycle" rel="noopener noreferrer"&gt;lifecycle guide&lt;/a&gt; cover framework-specific setup.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it fits
&lt;/h2&gt;

&lt;p&gt;Univer is a good candidate when editing is part of the product rather than a separate export step:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A CRM can let sales teams edit quote assumptions and see totals recalculate.&lt;/li&gt;
&lt;li&gt;A finance product can provide a spreadsheet-like planning surface over application data.&lt;/li&gt;
&lt;li&gt;An education platform can let instructors create and update structured grade sheets.&lt;/li&gt;
&lt;li&gt;An operations tool can let users edit a workbook while application code validates and persists the result.&lt;/li&gt;
&lt;li&gt;An agent-enabled product can expose a narrow set of Facade operations after a human approves the proposed change.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The important design decision is to keep persistence and authorization in your application. A workbook snapshot is not a substitute for your database's access-control model.&lt;/p&gt;

&lt;h2&gt;
  
  
  Trade-offs and alternatives
&lt;/h2&gt;

&lt;p&gt;Univer is not a drop-in Microsoft Excel replacement. A spreadsheet editor is only one part of office compatibility. Importing and exporting complex XLSX files, server-side collaboration, and some advanced capabilities are separate product areas or commercial packages. The open-source quick start explicitly does not require a commercial license or Server SDK, but that does not mean every product capability is included under the same terms.&lt;/p&gt;

&lt;p&gt;The core repository uses Apache-2.0 licensing; review the license of each package you plan to ship, especially commercial extensions. Also check the &lt;a href="https://github.com/dream-num/univer/blob/dev/docs/API_STABILITY.md" rel="noopener noreferrer"&gt;API stability policy&lt;/a&gt; before depending on internal extension points.&lt;/p&gt;

&lt;p&gt;Choose based on the job:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;Better fit&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Univer&lt;/td&gt;
&lt;td&gt;An editable office surface with formulas, commands, plugins, and app integration&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AG Grid&lt;/td&gt;
&lt;td&gt;A high-performance data grid inside an application, not a full office editor&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Handsontable&lt;/td&gt;
&lt;td&gt;A spreadsheet-like grid when its commercial model and feature set fit&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SheetJS&lt;/td&gt;
&lt;td&gt;Reading, writing, and transforming spreadsheet files without building an interactive editor&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;If you only need to generate an XLSX export, a file-processing library is simpler. If users need to work inside a rich spreadsheet UI, Univer is much more relevant.&lt;/p&gt;

&lt;h2&gt;
  
  
  Watch the SDK integration demo
&lt;/h2&gt;

&lt;p&gt;The maintainers link to this integration walkthrough from the official README:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/1p-SMEiK6Kg" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;h2&gt;
  
  
  What to check before adopting it
&lt;/h2&gt;

&lt;p&gt;Prototype the exact operations your users need: formulas, copy and paste, large sheets, keyboard navigation, persistence, import/export, and mobile behavior. Test the version you intend to deploy rather than relying on a demo. For v1.5.1, read the release page and the v1.5.0 notes before upgrading; the v1.5.1 tag itself does not provide a detailed change summary.&lt;/p&gt;

&lt;p&gt;The project is also useful to study even if you do not adopt it. Its preset and plugin boundaries show how a complex editor can be assembled without forcing every application to load every feature.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Would you embed a spreadsheet directly in your product, or keep spreadsheet work in a separate tool and exchange files?&lt;/strong&gt; Try the &lt;a href="https://docs.univer.ai/" rel="noopener noreferrer"&gt;official demo&lt;/a&gt; and compare the integration cost with your current workflow.&lt;/p&gt;

&lt;h3&gt;
  
  
  Sources and further reading
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/dream-num/univer" rel="noopener noreferrer"&gt;GitHub repository&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.univer.ai/" rel="noopener noreferrer"&gt;Official documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://githubtrending.today/language/typescript/" rel="noopener noreferrer"&gt;GitHub Trending TypeScript snapshot&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/dream-num/univer/releases/tag/v1.5.1" rel="noopener noreferrer"&gt;v1.5.1 release&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/dream-num/univer/releases/tag/v1.5.0" rel="noopener noreferrer"&gt;v1.5.0 release notes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.univer.ai/guides/sheets/getting-started/installation" rel="noopener noreferrer"&gt;Installation and lifecycle guides&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Written by &lt;a href="https://github.com/playlikeboy" rel="noopener noreferrer"&gt;Shaswat Raj&lt;/a&gt; · &lt;a href="https://www.linkedin.com/in/sh20raj/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; · &lt;a href="https://youtube.com/@stackshade" rel="noopener noreferrer"&gt;StackShade on YouTube&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>typescript</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
    <item>
      <title>WFX-Loot: How to Audit GitHub Actions After the November 2026 Secret-Stealer Campaign</title>
      <dc:creator>Sh Raj</dc:creator>
      <pubDate>Sun, 15 Nov 2026 10:28:19 +0000</pubDate>
      <link>https://dev.to/sh20raj/wfx-loot-how-to-audit-github-actions-after-the-november-2026-secret-stealer-campaign-5f94</link>
      <guid>https://dev.to/sh20raj/wfx-loot-how-to-audit-github-actions-after-the-november-2026-secret-stealer-campaign-5f94</guid>
      <description>&lt;h1&gt;
  
  
  Why WFX-Loot matters to GitHub Actions users
&lt;/h1&gt;

&lt;p&gt;A GitHub repository is not only source code. Its workflows may access package tokens, cloud credentials, deployment keys, environment variables, and identity tokens used to request short-lived cloud access. A compromised maintainer account can therefore become a production security incident.&lt;/p&gt;

&lt;p&gt;Aikido's WFX-Loot investigation, checked on November 15, 2026, describes a campaign that began on November 10. Its report says 4,837 compromised GitHub accounts opened probe pull requests across 61,764 repositories. It also reports that 10,431 pull requests reached repositories through collaborator or organization access, and that 92% were still open in its snapshot.&lt;/p&gt;

&lt;p&gt;The report gives different counts for payload executions in its summary and detailed sections, so this article avoids repeating a precise execution total. The practical point is clear: a probe can indicate a compromised contributor account, and a workflow run can expose much more than visible repository secrets.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdyr2x27kngga14b5pqrz.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdyr2x27kngga14b5pqrz.jpg" alt="Aikido's official WFX-Loot explainer video thumbnail" width="480" height="360"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Thumbnail from Aikido's official WFX-Loot explainer. Source: &lt;a href="https://www.aikido.dev/blog/compromised-github-accounts-push-ci-secret-stealer-to-tens-of-thousands-of-repositories" rel="noopener noreferrer"&gt;Aikido investigation&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  How the campaign moved
&lt;/h2&gt;

&lt;p&gt;Aikido describes three stages:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Probe:&lt;/strong&gt; a compromised account opens a pull request titled &lt;strong&gt;docs: dependency audit notes&lt;/strong&gt; from a branch named &lt;strong&gt;wfx-docs&lt;/strong&gt;, confirming that its stolen token can write to the repository.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Payload:&lt;/strong&gt; the attacker adds code to an existing workflow, adds a shell helper and npm postinstall hook, or creates a temporary workflow on a randomly named chore branch.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cleanup:&lt;/strong&gt; the changes are reverted quickly and the workflow run and logs are deleted. A missing run number can become a more reliable clue than an obvious malicious file.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The payload attempts to collect runner environment variables, GitHub Actions secrets and variables, the workflow token, OIDC tokens, credential files, shell histories, and keys for cloud, package, infrastructure, and AI services. It can also try to persist by creating long-lived AWS keys, weakening role trust policies, or adding Azure federated credentials. Rotating the original GitHub secret is not enough if a new cloud identity has already been created.&lt;/p&gt;
&lt;h2&gt;
  
  
  Indicators to search for
&lt;/h2&gt;

&lt;p&gt;Search every repository where a compromised account had write access, including organization repositories and projects reached through collaborator permissions.&lt;/p&gt;

&lt;p&gt;Aikido lists these indicators:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Branches named &lt;strong&gt;wfx-docs&lt;/strong&gt;, &lt;strong&gt;chore/&lt;/strong&gt; followed by eight random characters, or &lt;strong&gt;ci-check-&lt;/strong&gt; followed by four digits.&lt;/li&gt;
&lt;li&gt;Pull request title &lt;strong&gt;docs: dependency audit notes&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Commit messages &lt;strong&gt;ci: refresh build cache&lt;/strong&gt;, &lt;strong&gt;ci: restore&lt;/strong&gt;, &lt;strong&gt;chore: add ci helper&lt;/strong&gt;, &lt;strong&gt;ci: cleanup&lt;/strong&gt;, or &lt;strong&gt;chore: add dependency audit workflow&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;A temporary workflow named like &lt;strong&gt;build-audit-xxxxxxxx.yml&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;.ci-xxxxxx.sh&lt;/strong&gt; helper and a new npm postinstall hook.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The absence of an artifact named wfx-loot, a cache entry beginning with wfx-, or a WFX marker in the step summary does not prove the repository is clean. The report says the workflow run itself was often deleted.&lt;/p&gt;
&lt;h2&gt;
  
  
  Audit pull requests with GitHub CLI
&lt;/h2&gt;

&lt;p&gt;This checks all pull-request pages for the exact probe title in one repository. Use a GitHub CLI session that can read every relevant pull request:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;OWNER&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"your-org"&lt;/span&gt;
&lt;span class="nv"&gt;REPO&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"your-repo"&lt;/span&gt;

gh api &lt;span class="s2"&gt;"repos/$OWNER/$REPO/pulls?state=all&amp;amp;per_page=100"&lt;/span&gt; --paginate \
  --jq &lt;span class="s1"&gt;'.[] | select(.title == "docs: dependency audit notes") | [.number, .user.login, .head.ref, .created_at] | @tsv'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Search local history for the reported commit messages and branch names:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git fetch --all --prune

git log --all --since=&lt;span class="s2"&gt;"2026-11-10T00:00:00Z"&lt;/span&gt; \
  --format=&lt;span class="s2"&gt;"%h %ad %s"&lt;/span&gt; --date=iso \
  --grep=&lt;span class="s2"&gt;"ci: refresh build cache\|ci: restore\|chore: add ci helper\|ci: cleanup\|chore: add dependency audit workflow"&lt;/span&gt;

git branch -a &lt;span class="o"&gt;|&lt;/span&gt; grep -E &lt;span class="s2"&gt;"wfx-docs|chore/[a-z0-9]{8}|ci-check-[0-9]{4}"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;These checks are useful, not exhaustive. A branch may have been deleted or a repository rewritten. For organization-wide coverage, use an organization owner or security administrator account and inspect repositories, audit logs, Actions history, and access grants centrally.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to do if you find an indicator
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;If you find only the probe:&lt;/strong&gt; investigate the account that opened it. Revoke its sessions and tokens, review OAuth grants and SSH keys, restore account access, and check every repository the account could write to. A probe is evidence of account compromise even if you cannot find a payload run.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If the payload ran:&lt;/strong&gt; assume every secret and cloud role available to that workflow was exposed. Rotate GitHub and package-registry credentials, deploy keys, cloud credentials, and API tokens. Revoke active cloud sessions where possible. Inspect AWS access keys and role trust policies, Azure federated credentials, GCP service-account keys, Kubernetes credentials, and Vault policies. Rebuild affected self-hosted runners from trusted images rather than assuming a cleanup script is enough.&lt;/p&gt;

&lt;p&gt;Also review automated package publishing jobs and any machine that installed a package version Aikido identified as affected. The report names a Packagist package and two Go module tags; follow its current advisory for exact versions and remediation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Harden GitHub Actions after the audit
&lt;/h2&gt;

&lt;p&gt;Start with least privilege. GitHub recommends explicitly limiting GITHUB_TOKEN permissions rather than relying on broad defaults.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;CI&lt;/span&gt;

&lt;span class="na"&gt;on&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;pull_request&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;push&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;branches&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s"&gt;main&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;

&lt;span class="na"&gt;permissions&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;contents&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;read&lt;/span&gt;

&lt;span class="na"&gt;jobs&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;test&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;runs-on&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;ubuntu-latest&lt;/span&gt;
    &lt;span class="na"&gt;permissions&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="na"&gt;contents&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;read&lt;/span&gt;
    &lt;span class="na"&gt;steps&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;actions/checkout@&amp;lt;full-commit-sha&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;run&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;npm ci&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;run&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;npm test&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Replace the placeholder with the verified full commit SHA for the action version you intend to use. Pin third-party actions to immutable SHAs and update them through reviewed dependency updates. Do not let untrusted pull-request code access production secrets. Keep deployment jobs separate, use protected environments, and require reviewers before a workflow can publish or deploy.&lt;/p&gt;

&lt;p&gt;OIDC can remove long-lived cloud secrets from GitHub, but it is not a magic shield. A compromised workflow with permission to request an identity token may still try to exchange it. Restrict cloud trust to the intended repository, branch, environment, audience, and workflow. GitHub's current OIDC reference documents immutable subject claims for repositories created after July 15, 2026; update cloud trust conditions to match the subject format your repository actually uses.&lt;/p&gt;

&lt;p&gt;Finally, isolate self-hosted runners and avoid sharing a runner between untrusted pull requests and production deployments. CI should receive only the credentials required for the current job, for the shortest time possible.&lt;/p&gt;

&lt;h2&gt;
  
  
  The takeaway
&lt;/h2&gt;

&lt;p&gt;WFX-Loot is a reminder that the CI runner is part of your production security boundary. A small workflow edit can expose cloud roles, package publishing, AI provider keys, and infrastructure credentials. A clean working tree is not proof that workflow history is clean.&lt;/p&gt;

&lt;p&gt;Audit every repository your account or organization can write to, then verify cloud trust relationships as carefully as GitHub secrets. Which part of your CI environment would be hardest to rebuild safely today: runner machines, cloud identities, or deployment credentials?&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources and further reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.aikido.dev/blog/compromised-github-accounts-push-ci-secret-stealer-to-tens-of-thousands-of-repositories" rel="noopener noreferrer"&gt;Aikido's WFX-Loot investigation and indicators&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.github.com/en/actions/tutorials/authenticate-with-github_token" rel="noopener noreferrer"&gt;GitHub: GITHUB_TOKEN permissions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax" rel="noopener noreferrer"&gt;GitHub Actions workflow permissions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.github.com/en/actions/reference/security/oidc" rel="noopener noreferrer"&gt;GitHub OpenID Connect reference&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cli.github.com/manual/gh_api" rel="noopener noreferrer"&gt;GitHub CLI API command reference&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.reddit.com/r/devops/comments/1xvx8t2/wfxloot_what_the_stealer_leaves_behind_after_you/" rel="noopener noreferrer"&gt;Developer discussion in r/devops&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.reddit.com/r/github/comments/1xvvlyd/my_github_account_was_compromised_in_the_wfxloot/" rel="noopener noreferrer"&gt;User report in r/github&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/mVZOJ6F4Gs8" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Author links: &lt;a href="https://github.com/playlikeboy" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; · &lt;a href="https://www.linkedin.com/in/sh20raj/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; · &lt;a href="https://youtube.com/@stackshade" rel="noopener noreferrer"&gt;StackShade on YouTube&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;AI disclosure: This article was prepared by an autonomous AI editorial agent from public sources. Incident details and defensive commands were checked against primary reporting and official GitHub documentation; no repository scan was run in this article.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>github</category>
      <category>devops</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Spree Commerce 6: Building Multi-Vendor Marketplaces With APIs and Agent Tools</title>
      <dc:creator>Sh Raj</dc:creator>
      <pubDate>Sun, 15 Nov 2026 10:27:01 +0000</pubDate>
      <link>https://dev.to/sh20raj/spree-commerce-6-building-multi-vendor-marketplaces-with-apis-and-agent-tools-1628</link>
      <guid>https://dev.to/sh20raj/spree-commerce-6-building-multi-vendor-marketplaces-with-apis-and-agent-tools-1628</guid>
      <description>&lt;h1&gt;
  
  
  Why Spree Commerce 6 is worth evaluating
&lt;/h1&gt;

&lt;p&gt;A marketplace is more than a product catalogue with multiple sellers. It needs seller onboarding, product review, commission rules, order splitting, returns, and payouts. A B2B store adds company accounts, buyer roles, negotiated pricing, purchase orders, and approval workflows. Building those capabilities one endpoint at a time can turn a commerce project into a long platform project.&lt;/p&gt;

&lt;p&gt;Spree Commerce 6 is an open-source, self-hosted commerce stack aimed at those more complex cases. The major 6.0 release arrived on October 27, 2026, and 6.0.4 shipped on November 12 with marketplace dashboard improvements and fixes. The agent tooling is also relatively new: the 6.0.3 release added an MCP server for store operations and agent skills for developers.&lt;/p&gt;

&lt;p&gt;This is a release-driven story rather than a claim that Spree is a brand-new repository trend. The useful signal is that the 6.0 line is actively adding marketplace and agent workflows.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxt2zyteb2rp7w835z3o3.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxt2zyteb2rp7w835z3o3.webp" alt="Official Spree diagram showing a marketplace connecting vendors to customers" width="426" height="376"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Official Spree multi-vendor architecture illustration, not a product screenshot. Source: &lt;a href="https://spreecommerce.org/" rel="noopener noreferrer"&gt;Spree Commerce&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  What Spree 6 includes
&lt;/h2&gt;

&lt;p&gt;Spree is a commerce backend with Store, Admin, and Seller APIs. The project also provides a TypeScript SDK, a React admin dashboard, a production-ready Next.js storefront, signed webhooks, and OpenTelemetry tracing.&lt;/p&gt;

&lt;p&gt;For a marketplace, the important workflow is:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;An operator invites a seller and collects the information required for onboarding.&lt;/li&gt;
&lt;li&gt;The operator approves the seller and reviews new products before publication.&lt;/li&gt;
&lt;li&gt;A customer checks out once, even when the basket contains products from several sellers.&lt;/li&gt;
&lt;li&gt;Spree splits the order into seller-specific orders so each vendor handles its own fulfilment.&lt;/li&gt;
&lt;li&gt;Commission rules determine what the marketplace keeps and what each seller earns.&lt;/li&gt;
&lt;li&gt;Payouts can be scheduled through Stripe Connect or recorded manually with a bank reference.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The B2B workflow is different but uses the same commerce core. Companies can have divisions and invited buyers; catalogs control what each company sees; price lists define customer-specific or volume pricing; and sales representatives can prepare draft orders for buyers to confirm.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbmo4fcbq3hie012jwuwg.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbmo4fcbq3hie012jwuwg.webp" alt="Official Spree B2B diagram showing a company, resellers, and customer groups" width="426" height="376"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Official Spree B2B workflow illustration, not a product screenshot. Source: &lt;a href="https://spreecommerce.org/" rel="noopener noreferrer"&gt;Spree Commerce&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  The newer agent workflow
&lt;/h2&gt;

&lt;p&gt;Spree 6 also adds an MCP server for store operations. A store administrator connects an assistant from the AI Agents settings page, signs in, and approves the permissions the assistant can use.&lt;/p&gt;

&lt;p&gt;The documented tools cover product and collection updates, catalog and price-list changes, CSV imports and exports, stock levels, purchase orders, seller actions, and reports. An agent does not receive more access than the person who approved the connection.&lt;/p&gt;

&lt;p&gt;This is useful for repetitive operational work, such as mapping a supplier spreadsheet to product fields, importing the products, adding them to a collection, and preparing them for publication. The permission boundary matters: an agent should not be treated as a super-admin simply because it can call an MCP tool.&lt;/p&gt;

&lt;p&gt;For developer workflows, the Spree agent skills provide project conventions and documentation to coding assistants. The repository's 6.0.3 release added the MCP server and skills; 6.0.4 then focused on marketplace dashboard improvements and fixes.&lt;/p&gt;
&lt;h2&gt;
  
  
  Create a local store
&lt;/h2&gt;

&lt;p&gt;The official local setup requires Node.js 24 or later, Git, and Docker. The project recommends the create-spree-app CLI:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx create-spree-app@latest my-store
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;The CLI scaffolds a new project and guides you through the available backend and storefront choices. Follow the generated setup instructions for the services you select. The official homepage currently shows this command as the local install path.&lt;/p&gt;

&lt;p&gt;For an existing Spree project, the 6.0 release notes document the upgrade path:&lt;br&gt;
&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx spree upgrade
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;Do not run an upgrade against production without a database backup and a staging test. The 6.0 line includes changes across the admin, seller, and API surfaces, so verify custom extensions and payment flows before deployment.&lt;/p&gt;

&lt;p&gt;To add the agent tooling to an existing project, the repository documents:&lt;br&gt;
&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;spree add ai
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;The command adds the project-specific agent configuration and skills. The MCP server for store operations is a separate runtime connection that the store administrator must approve.&lt;/p&gt;
&lt;h2&gt;
  
  
  What changed in 6.0.4
&lt;/h2&gt;

&lt;p&gt;The November 12 release includes marketplace-facing improvements such as seller dashboard work and diagnostics, alongside fixes to checkout and order calculations. It also follows a short 6.0 patch sequence: 6.0.1, 6.0.2, 6.0.3, and 6.0.4 were published between October 29 and November 12.&lt;/p&gt;

&lt;p&gt;That cadence is useful for active development, but it also means teams should read the changelog before upgrading. Check the exact migrations, API changes, and fixes that affect the extensions you use. A version number alone is not a compatibility guarantee.&lt;/p&gt;
&lt;h2&gt;
  
  
  Is Spree the right choice?
&lt;/h2&gt;

&lt;p&gt;Spree is a candidate when you need a self-hosted commerce backend with marketplace and B2B workflows already represented in the product model. It is especially interesting if you want to own the storefront, API, seller experience, and operational automation rather than paying a platform fee for a hosted marketplace product.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;Consider it when&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Spree&lt;/td&gt;
&lt;td&gt;You need self-hosted marketplace or B2B workflows and are comfortable operating the stack&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Medusa or Vendure&lt;/td&gt;
&lt;td&gt;You prefer a JavaScript-first headless commerce approach&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Saleor&lt;/td&gt;
&lt;td&gt;A GraphQL-centric headless commerce workflow fits your architecture&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Shopify&lt;/td&gt;
&lt;td&gt;You prefer a hosted platform and want to minimize infrastructure operations&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Self-hosting is not free operations. You still own database backups, background jobs, storage, payment configuration, shipping and tax integrations, monitoring, security updates, and seller support. Payout automation also depends on correctly configuring the payment provider and marketplace account model.&lt;/p&gt;

&lt;p&gt;The repository is BSD-3-Clause licensed. That makes the core source permissive, but check the current product and support terms for any commercial services or enterprise features you plan to use. Infrastructure and payment processing still have costs.&lt;/p&gt;
&lt;h2&gt;
  
  
  A practical evaluation plan
&lt;/h2&gt;

&lt;p&gt;Start with a sandbox and model one complete marketplace transaction: invite a seller, approve a product, place a basket containing items from two sellers, split the order, calculate commission, and record a payout. Then test a B2B company with a custom catalog and price list.&lt;/p&gt;

&lt;p&gt;Only after those flows work should you connect an AI agent. Begin with read-only reporting or a product import preview, then grant write actions one at a time. This lets you evaluate both the commerce workflow and the MCP permission model without handing an agent broad store access.&lt;/p&gt;

&lt;p&gt;Would you rather build marketplace operations yourself, or start with a commerce core that already models sellers, commissions, and order splitting?&lt;/p&gt;
&lt;h2&gt;
  
  
  Sources and further reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://spreecommerce.org/announcing-spree-commerce-6/" rel="noopener noreferrer"&gt;Spree Commerce 6 announcement and feature guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/spree/spree" rel="noopener noreferrer"&gt;Spree repository&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/spree/spree/releases/tag/v6.0.4" rel="noopener noreferrer"&gt;Spree 6.0.4 release notes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/spree/spree/releases/tag/v6.0.3" rel="noopener noreferrer"&gt;Spree 6.0.3 release notes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://spree.sh/" rel="noopener noreferrer"&gt;Local setup guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.youtube.com/playlist?list=PLS6J5hdfBWh0" rel="noopener noreferrer"&gt;Multi-vendor marketplace videos&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.youtube.com/playlist?list=PLGaEQzQ1Zh00" rel="noopener noreferrer"&gt;Marketplace seller guides&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;div class="crayons-card c-embed text-styles text-styles--secondary"&gt;
    &lt;div class="c-embed__content"&gt;
        &lt;div class="c-embed__cover"&gt;
          &lt;a href="https://www.youtube.com/playlist?list=PLS6J5hdfBWh0" class="c-link align-middle" rel="noopener noreferrer"&gt;
            &lt;img alt="" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fi.ytimg.com%2Fvi%2FgvAfngFwxq8%2Fhqdefault.jpg%3Fsqp%3D-oaymwEXCOADEI4CSFryq4qpAwkIARUAAIhCGAE%3D%26rs%3DAOn4CLBKH9bHuOEyVqSKayeNQRvdFpNTVw%26days_since_epoch%3D20772" height="270" class="m-0" width="480"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="c-embed__body"&gt;
        &lt;h2 class="fs-xl lh-tight"&gt;
          &lt;a href="https://www.youtube.com/playlist?list=PLS6J5hdfBWh0" rel="noopener noreferrer" class="c-link"&gt;
            
          &lt;/a&gt;
        &lt;/h2&gt;
          &lt;p class="truncate-at-3"&gt;
            Multi-vendor marketplace features built into Spree Commerce, the open-source eCommerce platform, each shown in the real admin dashboard and the seller's own ...
          &lt;/p&gt;
        &lt;div class="color-secondary fs-s flex items-center"&gt;
            &lt;img alt="favicon" class="c-embed__favicon m-0 mr-2 radius-0" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fwww.youtube.com%2Fs%2Fdesktop%2Fbb2198ae%2Fimg%2Ffavicon.ico" width="48" height="48"&gt;
          youtube.com
        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
&lt;/div&gt;






&lt;p&gt;&lt;em&gt;Author links: &lt;a href="https://github.com/playlikeboy" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; · &lt;a href="https://www.linkedin.com/in/sh20raj/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; · &lt;a href="https://youtube.com/@stackshade" rel="noopener noreferrer"&gt;StackShade on YouTube&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;AI disclosure: This article was prepared by an autonomous AI editorial agent from public sources. Setup and version notes were checked against upstream documentation; no live store was deployed in this run.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ecommerce</category>
      <category>opensource</category>
      <category>webdev</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
