Changeloop security policy
Changeloop takes the security of its web app and the data it handles seriously. If you believe you have found a vulnerability, we want to hear about it.
No access to your code
Changeloop's GitHub App has no permission to read your repository's files. From each pull request it reads the title and description, nothing else. GitHub's pull request permission would also allow reading diffs, so every Changeloop build is checked to make sure it never requests them. Anything that looks like a secret in a title or description is removed before a draft is written. GitLab and Bitbucket connections work differently, so this applies to GitHub only.
Reporting a vulnerability
Please email security@changeloop.dev with:
- A description of the issue and its potential impact.
- Steps to reproduce, with any proof-of-concept code or screenshots.
- The affected surface (changeloop.dev, app.changeloop.dev, api.changeloop.dev).
- Your name or handle for credit, if you want to be acknowledged.
We aim to acknowledge new reports within 3 business days and to keep you updated as we investigate.
In scope
changeloop.devand all subdomains we operate (app.changeloop.dev,api.changeloop.dev,teams.changeloop.dev).- The GitHub App integration, including its webhook endpoint and OAuth installation flow.
- The public JSON changelog feed and the embeddable widget script served to customer sites.
- Account, billing, and session management, including the Stripe integration.
Out of scope
- Vulnerabilities in third-party services we use or that you connect (for example AWS, OpenAI, Stripe, Google or GitHub); please report those directly to the vendor.
- Reports requiring physical access to a victim's device, social engineering of Changeloop staff, or denial-of-service through traffic volume.
- Issues already publicly disclosed.
- Theoretical issues without a demonstrated impact path.
Safe harbour
If you make a good-faith effort to comply with this policy during your security research, we will consider that research to be authorised, we will work with you to understand and resolve the issue quickly, and we will not pursue or support legal action related to your research.
Coordinated disclosure
We ask that you give us a reasonable opportunity to investigate and remediate before any public disclosure. We are happy to credit you in any public advisory once the issue is resolved.
Machine-readable
A /.well-known/security.txt is published per RFC 9116 with the same contact and policy URLs.