<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>noyalib</title>
  <link href="https://noyalib.com/atom.xml" rel="self" type="application/atom+xml"/>
  <link href="https://noyalib.com"/>
  <id>https://noyalib.com</id>
  <updated></updated>
  <entry>
    <title>Page not found — noyalib</title>
    <link href="https://noyalib.com/404/"/>
    <id>https://noyalib.com/404/</id>
    <updated></updated>
    <published></published>
    <summary>The address did not match a page on noyalib.com. It may be mistyped, or the page may have moved. The home page and the sitemap list everything that exists.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>About — who builds noyalib and why</title>
    <link href="https://noyalib.com/about/"/>
    <id>https://noyalib.com/about/</id>
    <updated></updated>
    <published></published>
    <summary>noyalib is built by Sebastien Rousseau with contributors. Why it exists, how it is run, and what it will and will not do.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>Compliance — what noyalib gives your audit</title>
    <link href="https://noyalib.com/compliance/"/>
    <id>https://noyalib.com/compliance/</id>
    <updated></updated>
    <published></published>
    <summary>The artefacts a regulated buyer asks for, in every noyalib release: a CycloneDX SBOM, SLSA level 3 provenance, sigstore signatures, vetted dependencies.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>Conformance evidence — what noyalib measures on every change</title>
    <link href="https://noyalib.com/conformance/"/>
    <id>https://noyalib.com/conformance/</id>
    <updated></updated>
    <published></published>
    <summary>406 of 406 official YAML test cases through six entry points, zero unsafe code, fifteen fuzz targets, Miri, and a 131-probe family scorecard rated A+.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>Contact — noyalib</title>
    <link href="https://noyalib.com/contact/"/>
    <id>https://noyalib.com/contact/</id>
    <updated></updated>
    <published></published>
    <summary>How to reach the noyalib maintainers: discussions for questions, issues for bugs and feature requests, and a private channel for security reports.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>Developer docs — install and use noyalib</title>
    <link href="https://noyalib.com/docs/"/>
    <id>https://noyalib.com/docs/</id>
    <updated></updated>
    <published></published>
    <summary>Install the library, the CLI, the language server, the MCP server and the WebAssembly build, with a ten-line example for each and links to the reference.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>The noyalib family — six products, one version</title>
    <link href="https://noyalib.com/ecosystem/"/>
    <id>https://noyalib.com/ecosystem/</id>
    <updated></updated>
    <published></published>
    <summary>Six products, one parser: the library, the serde_yaml drop-in, the CLI, the language server, the MCP server and the WebAssembly build, released at one version.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>Frequently asked questions — noyalib</title>
    <link href="https://noyalib.com/faq/"/>
    <id>https://noyalib.com/faq/</id>
    <updated></updated>
    <published></published>
    <summary>Short answers about noyalib: how it compares with serde_yaml and its forks, what it does with comments, tags and YAML 1.1, and how fast it is.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>Legal and privacy — noyalib</title>
    <link href="https://noyalib.com/legal/"/>
    <id>https://noyalib.com/legal/</id>
    <updated></updated>
    <published></published>
    <summary>The licences noyalib ships under, what the website collects (nothing), which third parties it contacts (none), and the trade marks it refers to.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>MCP server — let an AI agent edit YAML safely</title>
    <link href="https://noyalib.com/mcp/"/>
    <id>https://noyalib.com/mcp/</id>
    <updated></updated>
    <published></published>
    <summary>noyalib-mcp gives an assistant three tools to read and change YAML without losing a comment. Install with npx, configure Claude, Zed or Continue in one block.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>Replace serde_yaml with one line — noyalib migration</title>
    <link href="https://noyalib.com/migration/"/>
    <id>https://noyalib.com/migration/</id>
    <updated></updated>
    <published></published>
    <summary>serde_yaml is archived. Rename the package to noyalib-serde-yaml in Cargo.toml and keep every call site. Guides cover serde_yml, serde-yaml-ng and more.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>News and releases — noyalib</title>
    <link href="https://noyalib.com/news/"/>
    <id>https://noyalib.com/news/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes and announcements for noyalib and its five companion crates: a note when a release changes something that affects your documents.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.33 — one standard across six crates</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-33/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-33/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.33: every crate at one version, a repository standard across all six, a lossless-edit layout fix, and a demo on the real engine.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.34 — the reliability release</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-34/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-34/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.34: property tests, structure-aware and no_std fuzzing, the arbitrary feature, a parser fix, and the suite through every crate.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.35 — proofs, an Action, a VS Code extension</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-35/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-35/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.35: machine-checked input budgets, a wasip2 build, a GitHub Action, pre-commit hooks, a VS Code extension, stateless MCP tools.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.36 — stream positions and the suite as streams</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-36/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-36/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.36: CST stream errors located in the stream, the yaml-test-suite run as 7,488 streams, and the three scanner defects it found.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.37 — the npm package returns, gated</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-37/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-37/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.37: a lockstep release whose one change is the noyalib-wasm npm package gate, repaired for npm 12 and back to publishing.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.38 — every dependency pinned, on every workflow</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-38/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-38/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.38: no unpinned npm command left in any workflow, registry probes verify tarballs by hash, and a fixture that uses most of YAML.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.39 — twenty documents that break parsers</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-39/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-39/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.39: twenty spec-torture documents cross-checked against libyaml and go-yaml, and the three parser defects they uncovered.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.40 — every crate is an OpenSSF passing project</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-40/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-40/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.40: all six crates in the family now hold the OpenSSF Best Practices passing badge, each answered from its own verified evidence.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.41: dependency bumps and a look back</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-41/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-41/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.41: the September GitHub Actions bumps across the family, and a look at the three defects the corpus tests caught in v0.0.40.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.42: the editor extension ships</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-42/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-42/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.42: the VS Code extension is bundled, carries an icon and a licence, and the release can now publish it to the Marketplace.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.43: a publish step that will not rot</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-43/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-43/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.43: the VS Code publish step stops parsing error text, and the deadline on its credential is written down where it matters.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.53: green on Rust 1.99</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-53/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-53/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.53: every parser budget now applies to typed targets (GHSA-4xcc-23fx-w2wj), and the family stays green on Rust 1.99.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.54: safer defaults for untrusted input</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-54/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-54/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.54: bounded readers, an MCP server confined to one directory and strict by default, and atomic writes in the CLI.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.55: limits on every loader</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-55/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-55/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.55: every loader enforces every limit, long lines parse in linear time, and thirteen security advisories.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.56: no value too deep to drop</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-56/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-56/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.56: a nesting ceiling on every path, early max_events refusal, the MCP npm wrapper, and CVE requests for the advisories.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>noyalib v0.0.57: closer to the spec</title>
    <link href="https://noyalib.com/news/noyalib-v0-0-57/"/>
    <id>https://noyalib.com/news/noyalib-v0-0-57/</id>
    <updated></updated>
    <published></published>
    <summary>Release notes for noyalib v0.0.57: six parse fixes found by differential fuzzing, typed keys read as written, and safer CST edits.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>Playground — run the YAML parser in your browser</title>
    <link href="https://noyalib.com/playground/"/>
    <id>https://noyalib.com/playground/</id>
    <updated></updated>
    <published></published>
    <summary>Paste YAML and see the JSON the parser produces, then turn it back. The published noyalib-wasm bundle runs inside your tab; nothing is uploaded.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>Security and supply chain — noyalib</title>
    <link href="https://noyalib.com/security/"/>
    <id>https://noyalib.com/security/</id>
    <updated></updated>
    <published></published>
    <summary>No unsafe code, limits for untrusted input, signed and attested releases, SBOMs, cargo-deny, cargo-vet and a private reporting channel.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
  <entry>
    <title>Solutions — what noyalib does for each kind of YAML work</title>
    <link href="https://noyalib.com/solutions/"/>
    <id>https://noyalib.com/solutions/</id>
    <updated></updated>
    <published></published>
    <summary>Read YAML into Rust structs, replace serde_yaml without source changes, format and validate in CI, edit in your editor or by an agent, parse in the browser.</summary>
    <author><name>Sebastien Rousseau</name></author>
  </entry>
</feed>
