Skip to content

Security: ideal-postcodes/feedback

Security

SECURITY.md

Security Policy

Found a security issue in an Ideal Postcodes product? Please report it privately — do not open a public issue.

How to report

Preferred: use GitHub's private vulnerability reporting on this repo — Report a vulnerability. It's encrypted and routes straight to the team.

Email fallback: support@ideal-postcodes.co.uk with subject prefix [security].

Include:

  • Product affected (CLI, API, Address Finder, Postcode Lookup, skills, docs, etc.)
  • Version / endpoint / commit SHA
  • Steps to reproduce
  • Impact (what an attacker can do)
  • Any logs, requests, or PoC — redact your own credentials and any third-party data

We'll acknowledge within 2 working days and keep you updated as we triage and fix.

Scope

In scope — the products this tracker covers:

  • @ideal-postcodes/cli
  • Ideal Postcodes API (api.ideal-postcodes.co.uk)
  • @ideal-postcodes/address-finder, @ideal-postcodes/postcode-lookup
  • @ideal-postcodes/skills
  • docs.ideal-postcodes.co.uk

Out of scope — report in the relevant repo:

Please don't

  • Post vulnerabilities, exploits, or PoCs in public issues or PRs.
  • Include real API keys, user tokens, customer addresses, or other personal data — even in private reports. Redact and reference instead.
  • Run automated scans, brute force, or load tests against production. We can provide a sandbox if you need one — ask first.

Disclosure

We'll coordinate disclosure with you once a fix is released. Credit is given by default unless you'd rather stay anonymous.

There aren’t any published security advisories