arXiv (All)
open access
Context-Aware Trust Verification for Identity-Based Software Signing
Modern software release infrastructure uses identity-based software signing to associate software artifacts with a known identity. For example, registries such as npm and Docker Hub rely on Sigstore's identity-based software signing in their artifact provenance workflows. However, existing verificat
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- Why Johnny Adopts Identity-Based Software Signing: A Usability Case Study of Sigstore#144257
- xChk: Bring Your Own Identity -- Heterogeneous Assurance with Verifier-Determined Sufficiency#370288
- Measuring and Exploiting Implicit Trust in LLM Tool-Calling Pipelines#1012417
- Measuring and Exploiting Implicit Trust in LLM Tool-Calling Pipelines#965349
- Poking Around in the Dark: Why a Shared Understanding of Components Matters#1036717
Record · ID 1075960
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive