Registry · Data collection & curation · Govern research data
opendp/opendp
Live AHK-0028
Identity
- Repository
- opendp/opendp
- Repository id
- 336597985
Also filed on the survey's other hub.
Description
Editorial draft A differential-privacy framework in Rust; experimental features and domain assumptions are flagged for pinning.
The campaign that admitted it
2026-08-03__privacy-consent-retention-data-governance · · run type (the campaign's own designation) high-recall-map This campaign is placed on both hubs of this survey
High-coverage, effort-bounded map as of 2026-08-03 (AWAITING_INDEPENDENT_QA): adopt one append-only research-data lifecycle contract binding purpose, fields, identities, custody, linkage, retention, release and review; no generic deletion-receipt standard exists and no legal-applicability conclusion is drawn.
Claim wording is the campaign's own, including its shorthand — see the methodology glossary.
1 ledger row cites this repository.
The claim is the campaign's own record — its coverage and its judgments — quoted word for word. It is not this site's assessment of the repository.
Current metrics
- Stars
- 428
- Forks
- 78
- Watchers
- 11
- Language
- Rust
- License
- MIT
- Archived
- No
- Created
- Last push
- Topics
- differential-privacydp-programming-frameworkopendpprivacy
- Snapshot
- · retrieved UTC
Counts only. This site never publishes stargazer, watcher or contributor identities.
Weekly movement
First snapshot 2026-08-10 — weekly movement begins with the second.
Star history
Not yet backfilled. Source will read: an independently collected archive of the same platform's public events, plus our snapshots.
Trust marks
- Snapshot
- · retrieved UTC
- Entries hash (sha256, first 12)
-
46fcea8cb0e2— this hub's served data file — verifiable at /api/entries.json - Snapshot hash (sha256, first 12)
-
5029a1dd0e77— raw capture, shared by both hubs (not yet published) - Method version
- supervised beta (v3.3 taxonomy)
- Sealed record
- 2026-08-03__privacy-consent-retention-data-governance — named, not linked; the record is not public.
What we collect
Collected per entry, weekly, append-only and hash-attested — the full field list is on the data card. Aggregate public metrics only; no stargazer or contributor identities. The posted record is public and quotable; the collection run itself is not published.