1sealsemantic last-mile verification

Research / Finding

hardening: minimum threshold for withintegratedtimestamps

F-SIG-GO-THRESHOLD-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Read the evidence · View in research browse

Recorded evidence

—score not recorded
sigstore/sigstore-go #590Credited fixsigstore/sigstore-go

hardening: minimum threshold for withintegratedtimestamps

merged
details
Finding IDs
F-SIG-GO-THRESHOLD-001
Status
merged
Recorded credit
thanks @1seal for reporting this improvement

F-SIG-GO-THRESHOLD-001: Verification failures. Timestamp verification does not enforce the minimum integrated-time threshold. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-SIG-GO-THRESHOLD-001

Security area (1seal assessment): Integrity. Timestamp verification does not enforce the minimum integrated-time threshold. Reviewed 24 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.