Skip to content

v0.2.0 Release Notes

Release Date: November 15, 2026

Highlights

  • A content domain for the accuracy and attribution of published content: a claim its cited source does not support, a quotation not found in its source, a citation to an unreliable source.
  • Security findings span discovery to fix: root cause, product impact, exploit notes, verification, typed relationships to work items and fixes, and a disclosure lifecycle on one record.
  • Formal reports: render a FindingSet as pandoc-ready Markdown for DOCX or PDF, with a shareable audience that keeps exploit detail out.

Content domain

The new content package defines Issue, a problem with one claim or one of the sources it cites, and projects it into a Finding in the content domain:

  • the claim is the location: Location.Component is the claim ID, Location.File the document that holds it and Location.Snippet its statement;
  • claim:<id> and source:<ref> tags support filtering, and content.ClaimID(f) reads the claim back;
  • severity defaults to medium.

The package names twelve common rules a claim checker can share, including content.quote.notFound, content.facts.missing, content.source.unreliable and content.claim.singleSource.

The shared status lifecycle carries a content finding through a review funnel: a static scan opens it, a model or a person confirms or dismisses it, and it is resolved when the claim or citation is fixed, or accepted as it is.

Security analysis and disclosure

  • Finding gains typed Relationships (threat, control, requirement, tracking item, fix, test, duplicate) and Verification.
  • security.Vulnerability gains RootCause, Impact, Exploit and Publication: visibility, disclosure state, GHSA, CVE, OSV and Go vulnerability IDs, and affected version ranges.
  • security.Exception.Rationale records why a risk was accepted.

Reports

The report package renders a FindingSet as a formal Markdown report: a pandoc metadata block, an executive summary and severity tables, a linked overview, and a section per finding. The shareable audience omits exploit detail, evidence payloads and code snippets; the internal audience includes them.

Compatibility

All additions are new types, fields and constants. Existing findings serialize and validate unchanged. Domains() now includes content.