Security

Last reviewed 25 September 2026

Beta v1.1 — Pumpkin Squashing is in beta testing. You may run into bugs or glitches here and there. Thank you for your patience.

Found a security problem with this site? Please tell us before telling anyone else.

Placeholder text. Read it against how the site actually behaves before launch, and have counsel look at anything that makes a promise.

Reporting a vulnerability

Email admin@projectresearchllc.com with what you found. A machine-readable version of this contact, following RFC 9116, is published at /.well-known/security.txt.

What helps in a report

• What you did, step by step, and what you expected instead.
• The impact, as you understand it — what it would let someone do.
• Whether you have a proof of concept, and if so, include it.
• The device, browser, and version you used to find it.

Scope

In scope: this site's own pages, scripts, and assets at www.pumpkinsquashing.com. This is a static, no-account, no-backend site — there is no login to attack and no server-side application beyond the file host itself, so reports about those are still welcome but may be answered as "expected behaviour" if they describe how static hosting works generally rather than a flaw specific to this site.

What not to do

• Don't run automated scanners or load tests against the live site without asking first.
• Don't access, modify, or attempt to access data that isn't yours — in practice, there isn't any visitor data held to access.
• Don't publicly disclose a report before we've had a reasonable chance to respond.

What to expect from us

An acknowledgement of your report, a straight answer on whether it's something we're fixing, and credit if you'd like it once it's resolved. We don't currently run a paid bounty program.

Safe harbour

Good-faith security research conducted consistent with this page will not be treated as unauthorized use, and we will not pursue legal action over it.