Tech News
← Home  ·  All topics

Yaml

4 GoKawiil briefs on this topic

New config format SOML released as draft spec by Sindre Sorhus

A new configuration file format called SOML (Sindre's Objectively Marvelous Language) has been published as a draft specification. It aims to combine JSON's strict, unambiguous parsing with YAML's readability, adding native support for comments, dates, instants, durations, and block strings while requiring no quotes on keys or braces at the top level. The author describes it as a draft and is inviting feedback from the community.

Open-source project formalizes IRS tax forms as citable, machine-checkable data

A proof-of-concept project encodes US federal individual income tax forms and instructions as YAML files, each line tied to a citation of the archived IRS source page it was drawn from. A build process and a citations checker verify that every line, parameter and gate has a traceable citation, and the software uses this data to run a self-preparation interview that computes values without ever filing or transmitting return data. Much of the encoding was produced by language-model agents, but the authors say the structure lets anyone verify its citations independent of who wrote it.

Jevotron launches CLI tool for anomaly detection across file formats

Jevotron is a new command-line tool that scans files such as CSV, YAML, JSON, TOML and OBO for anomalies, producing field-level probability scores and a review queue. The tool caches results in SQLite so unchanged entries aren't reassessed on subsequent runs, and users can guide scans with text instructions or a local Python config. A pilot test on 24 public agent traces reported the tool matched 130 of 163 step-quality labels (79.8% accuracy), with 89.7% precision and 70.3% recall for identifying harmful steps.

New CLI tool Confdiff diffs config files by meaning, not text, and hides secrets

Confdiff is a command-line and browser-based tool that compares JSON, YAML, TOML, INI, .env, properties, CSV and XML files by parsing them into a data model rather than comparing raw text. This lets it ignore cosmetic changes like key reordering, reformatting or added comments while flagging genuine differences, including type changes such as a number becoming a string. A --redact flag masks secret values with stable fingerprints so teams can see that credentials changed without exposing the actual values in a PR or CI log.