A scoped review of the key handling, the IPC boundary, the keystore format handling and the updater, by someone outside the project. Findings filed as issues here, each closed by a commit or accepted in writing on the issue.
Operator decision to record here before starting
Who reviews, the budget, and whether a public bounty follows.
Acceptance
The report is linked from the release notes of the first tagged release with no open critical or high finding.
Depends on
The threat model; the secret handling audit.
Parent: #10
## Scope
A scoped review of the key handling, the IPC boundary, the keystore format handling and the updater, by someone outside the project. Findings filed as issues here, each closed by a commit or accepted in writing on the issue.
## Operator decision to record here before starting
Who reviews, the budget, and whether a public bounty follows.
## Acceptance
The report is linked from the release notes of the first tagged release with no open critical or high finding.
## Depends on
The threat model; the secret handling audit.
grenade
added the child label 2026-09-15 12:42:05 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Parent: #10
Scope
A scoped review of the key handling, the IPC boundary, the keystore format handling and the updater, by someone outside the project. Findings filed as issues here, each closed by a commit or accepted in writing on the issue.
Operator decision to record here before starting
Who reviews, the budget, and whether a public bounty follows.
Acceptance
The report is linked from the release notes of the first tagged release with no open critical or high finding.
Depends on
The threat model; the secret handling audit.