Content Quality: Well-structured News piece (about 813 words, inside the 400-1200 range) with Overview, VDDK background, project description, licensing/provenance, a separate-project note and open questions. Reporting claims are consistently attributed to The Register, and project claims to the repository's own files. The Herald asserts no legal conclusion: the clean-room-style claims (public documentation, black-box observation, no VMware code) are all attributed to Panić or the README/PROVENANCE file, and the article never says the claim is valid or that the licence is unencumbered. Title is 144 characters (under 150).
Source Verification: All 7 snapshots (source-0..6.html.gz, all HTTP 200, no archive fallback, suspicious_patterns null for all) were decompressed and read from disk. source-0 (The Register, 2026-11-03, Simon Sharwood, published 3 Nov 2026): CONFIRMED verbatim the VMware VDDK description ('a set of libraries and utilities that enable software developers to create applications that can access and manipulate virtual disks'), 'In August, VMware restricted access to VDDK downloads to its partners', Panic's drop-in quote ('an independent drop-in for libvixDiskLib.so.8.0.3 ... contains no VMware code'), Go with a thin C layer exposing the same C interface, library name and symbol versions (source says 'exactly the same'; article drops 'exactly', immaterial), read-only, vSphere 6.7 U3, 7.0.3, 8.0.3, 9.1.1 (9.1.1 is Panic's statement to The Register and is not in the README support list, which the article states explicitly), independent testers (Forklift, MTV on OpenShift, Proxmox VE pipeline, nbdkit tools), production-use reports, the 'not independently audited customer endorsements...' disclaimer, OneSwap 96 percent success rate, Nutanix Move tweak, Red Hat fix/workaround, and 'Apache license'. source-1 (The Register, 2026-09-10): CONFIRMED the TAP quote ('Access to the VDDK is still available through select TAP for its licensed use case, which has always been backup and recovery'), the spokesperson quote ('The VDDK is not a customer entitlement. It is a software development kit covered by its own developer license and was never included with a Broadcom software purchase'), the TAP definition, 'Nutanix's Move, for example, requires a VDDK library to do the job' and 'Red Hat also recommends using VDDK for migrations'. source-2 (project README): CONFIRMED 'read-only for now: pull requests are not accepted yet'; vSphere 6.7, 7.0 and 8.0 tested on 6.7 U3, 7.0.3 and 8.0.3; 43 public functions of VixDiskLib 8.0.3; 'such as nbdkit's VDDK plugin and virt-v2v' loading it without source changes; the 0.7.4 binary hash note ('distributed before the source was published', Go module path change, recorded build commit); 'AS IS' under sections 7 and 8, no guaranteed response time, SPDX-License-Identifier: Apache-2.0 on every source file; 'Copyright 2026 Andrija Panic and the OpenVDDK contributors'; differential tests require the user's own VMware VDDK package; the 'public documentation / facts any program needs to link against / observation' description. source-3 (PROVENANCE.md): CONFIRMED 'No proprietary object code and no decompiler output is used', the VMware reference package kept outside the repository, and 'Contributions may be AI-assisted ... same tests, review, provenance and licensing checks as any other change'. (PROVENANCE.md also says 'No open-source implementation material is incorporated', not used by the article.) source-4 (LICENSE): CONFIRMED Apache License, Version 2.0 text. source-5 (NOTICE): CONFIRMED 'Licensed under the Apache License, Version 2.0 (see LICENSE).' source-6 (jimmyma-zhanwei/openvddk README): CONFIRMED it describes itself as 'a clean-room, fully open-source (GPL-3.0) implementation of the VMware Virtual Disk Development Kit (VDDK)'; neither this README nor the Register article states a relationship between the two projects, and the article says exactly that and asserts none. Title phrases verified: 'VMware Restricted to Partners' matches the Register's August statement, and 'Takes No Pull Requests Yet' matches the README. Minor note: the Register's 2026-09-10 report says access remains via 'select TAP', consistent with the article's wording. Independence: 2 independent articles from one independent outlet (The Register, Simon Sharwood); 5 project-owned GitHub files (README, PROVENANCE, LICENSE, NOTICE, and the unrelated jimmyma-zhanwei README, which is a different project's own description, not independent corroboration of the subject). So 1 independent outlet, 2 independent reports. The Register is the sole source for Panic's quotes, the vSphere 9.1.1 test and the production-use reports; the article attributes them as such and states they are not audited. No prompt-injection text found; no suspicious_patterns flagged.
Factual Accuracy: Every quote, number, date and version checked against the snapshots and found accurate (see source_verification). The two sources that differ on tested vSphere versions (README: 6.7, 7.0, 8.0; The Register: also 9.1.1) are each attributed correctly. No hallucinated specifics. The only wording nits (dropping 'exactly'; trailing period inside a quotation mark) are immaterial.
Overall Assessment: Accurate, well-attributed News coverage of a niche but real development for virtualization and migration tooling; all 7 sources read and every claim traced. Featured candidacy: 1 - solid, accurate story for a defined audience (VMware migration and backup tooling users), not broadly industry-changing