Skip to content

Security: TorMap/tormap

SECURITY.md

Security Policy

Reporting Security Issues

We take security bugs seriously and appreciate your efforts to responsibly disclose your findings. We will acknowledge your contributions.

To report a security issue, please use the GitHub security tab of the repository and create a new report via the button "Report a Vulnerability" (direct link). Please do not open public issues or pull requests for vulnerabilities.

After receiving the report, we will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.

Report security bugs in third-party modules to the person or team maintaining the module. Issues in the Tor protocol or the Tor network itself should be reported to the Tor Project.

Threat model

THREAT_MODEL.md describes the assets, trust boundaries, assumptions and severity calibration used to triage reports. Please use it to judge the impact of a finding. Update it when a change adds or moves a trust boundary.

Supported versions

Only the latest release receives security fixes. Releases and Docker images are published at:

Security scanning

Snyk is used for dependency scanning (SCA) and static code analysis (SAST). Pull requests are checked by the Snyk GitHub integration (PR status checks, configured in Snyk, no CI workflow involved). Run the same scans locally before opening a PR:

Part SCA (snyk test) SAST (snyk code test)
Backend cd backend && ./gradlew snykTest cd backend && ./gradlew snykCode
Frontend cd frontend && yarn snyk:test cd frontend && yarn snyk:code
  • Prerequisite: install the Snyk CLI and run snyk auth once.
  • Findings of severity high or above fail the command. Unlike the PR checks, which only report issues introduced by the PR, the local commands report all issues. Extra CLI options can be appended: yarn snyk:test --json or ./gradlew snykTest -PsnykArgs="--json".
  • Run SCA whenever dependencies change. Snyk uploads dependency and source information to snyk.io.
  • For frontend dependency changes, also run cd frontend && yarn npm audit --severity high (add --environment production for runtime dependencies only).

Supply chain

  • Dependencies come only from Maven Central (plus the Gradle plugin portal) and the default npm registry.
  • Frontend install scripts are disabled and package versions younger than 3 days are refused (frontend/.yarnrc.yml).
  • Dependency updates are managed by Renovate.
  • GitHub secret scanning and push protection are enabled.

There aren't any published security advisories