Paper

{
  "raw_xml": "<entry>\n    <id>http://arxiv.org/abs/2603.17133v1</id>\n    <title>A Longitudinal Study of Usability in Identity-Based Software Signing</title>\n    <updated>2026-03-17T20:53:46Z</updated>\n    <link href='https://arxiv.org/abs/2603.17133v1' rel='alternate' type='text/html'/>\n    <link href='https://arxiv.org/pdf/2603.17133v1' rel='related' title='pdf' type='application/pdf'/>\n    <summary>Identity-based software signing tools aim to make software artifact provenance verifiable while reducing the operational burden of long-lived key management. However, there is limited cross-tool longitudinal evidence about which usability problems arise in practice and how those problems evolve as tools mature. This gap matters because unusable signing and verification workflows can lead to incomplete adoption, misconfiguration, or skipped verification, undermining intended integrity guarantees.\n  We conducted the first mining-software-repositories study of five open-source identity-based signing ecosystems: Sigstore, OpenPubKey, HashiCorp Vault, Keyfactor, and Notary v2. We analyzed approximately 3,900 GitHub issues from Nov. 2021 to Nov. 2025. We coded each issue for the reported usability concern and the implicated architectural component, and compared patterns across tools and over time. Across ecosystems, reported concerns concentrate in verification workflows, policy and configuration surfaces, and integration boundaries. Longitudinal Poisson trend analysis shows substantial declines in reported issues for most ecosystems. However, across usability themes, workflow- and documentation-related concerns decline unevenly across tools and concern types, and verification workflows and configuration surfaces remain persistent friction points. These results indicate that identity-based signing reduces some usability burdens while relocating complexity to verification semantics, policy configuration, and deployment integration. Designing future signing ecosystems therefore requires treating verification semantics and release workflows as first-class usability targets rather than peripheral integration concerns.</summary>\n    <category scheme='http://arxiv.org/schemas/atom' term='cs.SE'/>\n    <category scheme='http://arxiv.org/schemas/atom' term='cs.CR'/>\n    <published>2026-03-17T20:53:46Z</published>\n    <arxiv:primary_category term='cs.SE'/>\n    <author>\n      <name>Kelechi G. Kalu</name>\n    </author>\n    <author>\n      <name>Hieu Tran</name>\n    </author>\n    <author>\n      <name>Santiago Torres-Arias</name>\n    </author>\n    <author>\n      <name>Sooyeon Jeong</name>\n    </author>\n    <author>\n      <name>James C. Davis</name>\n    </author>\n  </entry>"
}