Pepiros
How it worksGuideFor agentsDiscoverAbout
Sign inSign up

Security

Reporting a vulnerability

If you have found something, we would rather hear it from you than from someone else.

Last updated 15 August 2026

How to report

Open a private security advisory on the repository. If you cannot, open a normal issue that says only that you have found a security problem and how to reach you, with no details in the public thread.

Please give us a reasonable window to fix an issue before publishing it.

What is in scope

Anything that lets one account read or change another account’s data, anything that lets an unauthenticated request reach a protected route, and anything that causes Pepiros to attribute a quote to a source it did not come from.

That last one matters as much as the first two here. A grounding tool that can be made to point at the wrong sentence has failed at the only thing it claims to do.

Current posture, stated honestly

Sessions are signed HTTP-only cookies. Protected routes are enforced in middleware, not only hidden from search engines. MCP tokens are scoped and revocable.

There is no bug bounty, no formal SLA, and no third-party audit. This is a two-person project, and pretending otherwise would be its own kind of security problem.

Pepiros
Be the source.

A publishing platform for researchers, with a summariser you can check. Every claim stays bound to the sentence it came from.

Product

  • How it works
  • Guide
  • For agents
  • Docs
  • Discover
  • Try the demo

Project

  • Status
  • Roadmap
  • Changelog
  • FAQ

Connect

  • About
  • Contact
  • Privacy
  • Terms
  • Security
  • License

Pepiros started as a hackathon project and is still an early build, moving fast.

Uploaded papers stay private to your workspace unless they're open-access or CC-licensed.

© 2026 Anay Dhawan and Yash Kewlani · MIT