{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihez3clcgxwi2lwa2ocie6xz3cadkfb6ikidaxbkrfealg3u4pl64",
    "uri": "at://did:plc:azwgjkqilqtufnhrpl2oxmkw/app.bsky.feed.post/3mhsgswjw3bf2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreihq5uccmkdfezknnvzcfjekz7riq3il26dag7zbfgjmylev6vxmbe"
    },
    "mimeType": "image/jpeg",
    "size": 44024
  },
  "path": "/2026/03/netrise-provenance-open-source-risk/",
  "publishedAt": "2026-03-24T10:25:06.000Z",
  "site": "https://nerds.xyz",
  "tags": [
    "Open source",
    "Enterprise",
    "Security",
    "cybersecurity",
    "DevSecOps",
    "Linux",
    "NetRise",
    "NetRise Provenance",
    "open source risk",
    "open source security",
    "SBOM",
    "software supply chain",
    "XZ Utils"
  ],
  "textContent": "NetRise Provenance promises to map open source code back to the people behind it after the XZ backdoor scare. That raises some big questions.",
  "title": "NetRise Provenance wants to track who writes your open source code after XZ backdoor scare"
}