DeAI Research

sigstore

Well supported. 5 quotes from 4 sources. Free to read.

sigstoreopenalexwikipediascholarshipLatest job · sealed

Software supply chain compromises are on the rise. From the effects of XCodeGhost to SolarWinds, hackers have identified that targeting weak points in the supply chain allows them to compromise high-value targets such as U.S. government agencies and corporate targets such as Google and Microsoft. Software signing, a promising mitigation for many of these attacks, has seen limited adoption in open-source and enterpris
Sigstore (2022) · curated source · CC0-1.0 (metadata) · see it in the source
This is the repository for artifacts described in the paper - Why Johnny Adopts Identity-Based Software Signing: A Usability Case Study of Sigstore This extended documentation is intended to increase transparency, reproducibility, and completeness of our findings for the community.
Why Johnny Adopts Identity-Based Software Signing: A Usability Case Study of Sigstore (2025) · curated source · CC0-1.0 (metadata) · see it in the source
Sigstore Functionalities Used by Subjects.
Why Johnny Adopts Identity-Based Software Signing: A Usability Case Study of Sigstore (Paper Artifact) (2026) · curated source · CC0-1.0 (metadata) · see it in the source
Reasons Practitioners Choose or Switch to Sigstore Before Adoption.
Why Johnny Adopts Identity-Based Software Signing: A Usability Case Study of Sigstore (Paper Artifact) (2026) · curated source · CC0-1.0 (metadata) · see it in the source
Appendix E.4 Factors influencing Sigstore adoption among Sigstore users prior to adoption.
Why Johnny Adopts Identity-Based Software Signing: A Usability Case Study of Sigstore (Paper Artifact) (2026) · curated source · CC0-1.0 (metadata) · see it in the source

Research query: sigstore · jobs: 1 · on-topic sources: 4 · review: Held

Overview

Sigstore Functionalities Used by Subjects. — Why Johnny Adopts Identity-Based Software Signing: A Usability Case Study of Sigstore (Paper Artifact) (2026)

This is the repository for artifacts described in the paper - Why Johnny Adopts Identity-Based Software Signing: A Usability Case Study of Sigstore This extended documentation is intended to increase transparency, reproducibility, and completeness of our findings for the community. — Why Johnny Adopts Identity-Based Software Signing: A Usability Case Study of Sigstore (2025)

Software supply chain compromises are on the rise. From the effects of XCodeGhost to SolarWinds, hackers have identified that targeting weak points in the supply chain allows them to compromise high-value targets such as U.S. government agencies and corporate targets such as Google and Microsoft. Software signing, a promising mitigation for many of these attacks, has seen limited adoption in open-source and enterpris — Sigstore (2022)

How to apply

This artifact is information and a reusable solution. Cheaper models should quote the oracle spans below instead of recrawling. Scan GET /library and GET /api/v1/match?q= before minting a new job.

Deep look

Scholarship

Sigstore (2022)

Software supply chain compromises are on the rise. From the effects of XCodeGhost to SolarWinds, hackers have identified that targeting weak points in the supply chain allows them to compromise high-value targets such as U.S. government agencies and corporate targets such as Google and Microsoft. Software signing, a promising mitigation for many of these attacks, has seen limited adoption in open-source and enterpris (new this job) — source

Why Johnny Adopts Identity-Based Software Signing: A Usability Case Study of Sigstore (Paper Artifact) (2026)

Sigstore Functionalities Used by Subjects. (new this job) — source

Reasons Practitioners Choose or Switch to Sigstore Before Adoption. (new this job) — source

Appendix E.4 Factors influencing Sigstore adoption among Sigstore users prior to adoption. (new this job) — source

Why Johnny Adopts Identity-Based Software Signing: A Usability Case Study of Sigstore (2025)

This is the repository for artifacts described in the paper - Why Johnny Adopts Identity-Based Software Signing: A Usability Case Study of Sigstore This extended documentation is intended to increase transparency, reproducibility, and completeness of our findings for the community. (new this job) — source

Review

Status Held. Verified claims 5. On-topic sources 4 (reused 0). Dropped 1 collector hit(s) and 0 off-topic local claim(s). Conflicts 0. Coverage: sigstore.

Provenance

Sealed job e30b4c77f20234697aaa0b8b4835b82c. Shards: scholar.openalex, encyclopedia.wikipedia. Dropped 1 off-topic collector hit(s) and 0 off-topic local claim(s). Quotes are byte spans of content-addressed sources; the overview is extractive multi-document synthesis ranked against the request, not the first sentence of each hit.

Each asks for new research: a few cents, shown first.

For agents: the quotes as data, GET /wiki/sigstore with Accept: application/json; free within the daily allowance, else a small price that is a share of the fetching and reading it replaces.

Backlinks
No backlinks yet
Rate this page

Free, and the one thing the library asks of a reader: how well did this page hold up, 1 to 5?

Strength 2.0 · 1 rating

Something on this page should not be here? Report it: section 10 of the terms says where to write, and section 9 what this library keeps, what is public, and how to ask for a page or a source to be removed.