Skip to content

0.4.0 - 2026-10-15

Choose a tag to compare

View all tags
@github-actions github-actions released this 15 Oct 10:10
v0.4.0
1c77a27
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Release Notes

piiflow datamap writes and maintains a full Fides data map of a repository: its systems, what
they store, where they send personal data and what they receive, and a proposed privacy
declaration per purpose, from one offline command. Re-runs merge into the map a person keeps.
scan and diff output is unchanged: for the same input, 0.4.0 reports the same flows and
findings as 0.3.1.

Added

  • piiflow datamap: a full Fides data map of the repository (.fides/datamap.yml), maintained
    in place (docs, ADRs 0018 and 0019).
    • Systems: one per deployable service: C# web, worker and executable projects; packages with
      a server or app framework; Django and Python app objects; Dockerfiles. Or as declared under
      the new systems: key of .privacy-flow.yml.
    • Flows between systems: requests through registered clients (typed AddHttpClient<T>,
      axios.create, httpx, aiohttp) resolve to the system their base address names, by
      .NET Aspire project names, docker-compose services and systems: hosts:.
    • Flows to processors and unnamed destinations, and each system's input from users.
    • Datasets: from Entity Framework Core, Django, SQLAlchemy and Prisma models, with fields
      classified like flows.
    • Privacy declarations, proposed: a data use per group of evidence, from
      catalogue/topology/purposes.yml, always listed for review, never with a legal basis.
    • Re-runs merge into the file over the last generation (.fides/datamap.lock.json):
      edits, deletions and additions stay, untouched values follow the code.
    • privacy-datamap: decisions in its manifest win.
    • CI: --check exits 5, a new exit code, when the map is out of date. The GitHub Action
      gains datamap-check.
  • On dotnet/eShop: 11 services, 4 datasets (with the order's card number and address), and the
    web app's request carrying them resolved to the ordering API. The smoke test checks them.
  • The flow-facts document can carry a topology section; only datamap writes it. scan and
    diff output is unchanged.

Install privacy-flow 0.4.0

Install prebuilt binaries via Homebrew

brew install noru-tech/tap/piiflow

Download privacy-flow 0.4.0

File Platform Checksum
privacy-flow-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
privacy-flow-x86_64-apple-darwin.tar.xz Intel macOS checksum
privacy-flow-aarch64-unknown-linux-musl.tar.xz ARM64 MUSL Linux checksum
privacy-flow-x86_64-unknown-linux-musl.tar.xz x64 MUSL Linux checksum

Verifying GitHub Artifact Attestations

The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:

gh attestation verify <file-path of downloaded artifact> --repo noru-tech/privacy-flow

You can also download the attestation from GitHub and verify against that directly:

gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation> --repo noru-tech/privacy-flow
Assets 16
Loading