Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Run and publish the Milestone 5 Burp CE parity audit

Open
  • Is something wrong?
#68 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
security, testing-qa

Research direction

Start with the capability matrix and docs/burp-parity.md, then read the roadmap and README to understand the stated scope and deviations. Exercise representative workflows against authorized local practice targets and PortSwigger Academy labs using the 0.1.x/current release. Record steps, results, evidence, gaps, release, date, and environment; completion means every matrix row has a current status and evidence, gaps are linked or explicitly out of scope, and the audit is repeatable and linked from docs/burp-parity.md.

Written by the indexing model from the issue text.

Description

documentation help wanted priority: p2

Context

The capability matrix is a direction, not a completed audit. Milestone 5 requires
a documented parity audit before Perseid can claim CE manual-toolkit parity
subject to the stated deviations.

Proposal

  • Audit every capability row against the 0.1.x/current release using the
    definition of done: usable without developer tools, tested, documented safety
    behavior, and an up-to-date matrix.
  • Exercise representative workflows against local practice targets and
    PortSwigger Academy labs.
  • Record exact commands/steps, observed behavior, gaps, and deviations.
  • File focused issues for every gap; update statuses and milestone assignments.
  • Re-check deliberate deviations (external browser, no BApp compatibility, no
    Intruder throttling, keyboard-first, persistence extra).
  • Publish the audit date, release, and environment.

Acceptance criteria

  • Every matrix row has a current status and evidence.
  • Gaps have linked issues or are explicitly non-goals/deviations.
  • The audit uses only authorized test systems and synthetic evidence.
  • The matrix, roadmap, README, and docs agree on what is working.
  • The audit is repeatable and linked from docs/burp-parity.md.
Dominant language
Rust
Stars
1
Forks
0
Avg merge
34m
Merged PRs (30d)
66

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from andyintheshell/perseid

All issues in andyintheshell/perseid

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.