1sealsemantic last-mile verification

Research / Finding

feat(ngclient): require explicit bootstrap argument

F-TUF-PYTUF-002

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
theupdateframework/python-tuf #2903Security PRtheupdateframework/python-tuf

feat(ngclient): require explicit bootstrap argument

merged
details
Finding IDs
F-TUF-PYTUF-002
Status
merged
Reported date
Rationale
prevents accidental insecure bootstrap behavior by requiring explicit bootstrap intent.
PR opened by
@1seal
PR state observed
closed; GitHub merged: true; 2026-09-24
PR observation basis
Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed.
Contribution boundary
@1seal opened this PR; this alone does not establish sole code authorship.

F-TUF-PYTUF-002: Verification failures. Bootstrap handling requires an explicit trusted starting point. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-TUF-PYTUF-002

Security area (1seal assessment): Provenance. Explicit bootstrap makes the initial trusted metadata origin a caller decision; this is trust-root provenance hardening. 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.