Add provenance metadata to browser profiler JSON export - #339
Conversation
|
@lovishmenaria14-gif is attempting to deploy a commit to the yashkewlani2020-gmailcom's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Hey @lovishmenaria14-gif, your first PR on Fair Code, that's awesome, thank you. This project is about making AI more accountable, and contributions like yours are what keep that work going. We'll review your changes shortly. If you haven't already, give the contributing guide a quick read: it covers how audits are structured and what we look for in a review. |
|
Changes approved. The JS provenance path now covers the missing part of #327. One minor consistency issue: the SPEC/earlier implementation defines the engine value as python / js, while this uses javascript; please use js to keep the exported schema consistent. |
…ple data PR #339 added a provenance block to the "Copy as JSON" export, hashing currentFile - set once in readFile() and never updated afterward. The sample-data button and the ?demo auto-load both call runText() directly, bypassing readFile() entirely, so after a real upload followed by "Try it with a sample dataset," currentFile still pointed at the old real file while currentResult reflected the sample data. The exported provenance.dataset_hash would silently misrepresent which file produced the numbers. file now flows through runText()/runTable() as an explicit parameter instead of being set as a side effect in readFile(), so every path that reaches runTable() sets currentFile to the correct value (or null for in-memory data) rather than inheriting whatever the last real upload left behind. Co-Authored-By: Lovish Menaria <lovishmenaria14008@gmail.com>
3 participants
Changes
crypto.subtle.nulldataset hash with an explanatory note.Verification
sha256:<hex>dataset hash.assets/profiler-ui.jsrelative tomain.