EDAForge vs PocketBase

EDAForge's release feed shows a package changing identity between its first two tags. The v0.1.0 notes describe DataAudit, a data-quality auditing package built around audit_data(), reusable audit_rules() and audit_score(), with install instructions still pointing at vinodhpmd/DataAudit, while the repository now serves EDAForge. Only three tags exist, one of which is a bare compare link with no notes, and the most recent is a CRAN-policy cleanup rather than feature work.

The substance so far is all in the DataAudit-named 0.1.0: more than a dozen check families spanning missing values, duplicates, ranges, patterns, dependencies and grouped sequences, wrapped in a structured report object with print and summary methods. The 0.1.1 that follows removes a default output path, moves examples to tempdir() and adds an introductory vignette, which is the standard shape of a package being made acceptable to CRAN. The public identity is currently ahead of the release notes, so a reader arriving at the feed cannot tell from it what EDAForge does.

Expect the next tag to align the notes with the EDAForge name and add exploratory-analysis functions alongside the auditing core; the compliance pass in 0.1.1 points at a CRAN submission as the near-term goal.