Skip to content

Security: FetchDoge/permit

SECURITY.md

Security Policy

What this repository is

permit is a payment-authority scheme in which agents spend against permits rather than holding raw account access.

Reporting a vulnerability

Preferred: GitHub private vulnerability reporting. Open the Security tab on this repository and choose Report a vulnerability. That channel is private between you and the maintainer, requires no email, and nothing is posted publicly. Private reporting is enabled on this repository.

If you cannot use that channel, open a minimal public issue stating only that you have a security report and how to reach you. Please do not include exploit details, proof-of-concept code, or affected-version specifics in a public issue.

Scope

In scope: Any path where a permit can be replayed, reused beyond its scope, escalated to a descendant capability, or revoked-then-honoured; and any way a permit's recorded use can diverge from its actual use.

Out of scope / stated plainly: The scheme is a design and reference implementation. It has not been reviewed by a payment network or a financial auditor.

What to expect

Stage Commitment
Acknowledgement of your report within 7 days
Initial assessment and severity call within 14 days
Fix, or an agreed public disclosure coordinated with you

You will be credited in the fix or advisory unless you ask to remain anonymous.

What this policy does NOT offer

There is no bug bounty, and no monetary reward is offered or implied. This is an independent research project maintained by one person. What it can offer is a fast, honest response and public credit.

Related

  • Our agent-systems threat posture and the method behind these reviews: see the adversarial-seat repository for the review method, and hermes-refuse for the fail-closed execution posture.

There aren't any published security advisories