Skip to content

Security: jubeixu/ReviewTide

Security

.github/SECURITY.md

Security Policy

Supported versions

Version Supported
0.5.x yes
< 0.5 no

Reporting a vulnerability

ReviewTide parses offline exports you already have, so the surface is narrow but real:

  • unbounded memory on crafted numstat lines (huge path columns),
  • quadratic behaviour on adversarial PR export shapes,
  • report injection: author names and file paths from exports must be escaped so a crafted handle cannot smuggle markup into the rendered tables.

Please do not open a public issue for these. Contact the repository owner through the profile with:

  1. The affected version (reviewtide version or the commit SHA).
  2. The smallest synthetic export that triggers the behaviour.
  3. Expected vs. actual behaviour.

You will get an acknowledgement within a week. Fixes land in the next minor release and the reporter is credited in the changelog unless they prefer otherwise.

Scope

  • gitlog.py / prexport.py - untrusted input, primary focus.
  • flow.py / ownership.py - aggregation logic.
  • report.py - escaping of export-derived strings in output.

There aren't any published security advisories