Security

This page lists the security controls we run today, so you can check them instead of taking our word for it. Where a control has a limit, we say so.

Automated code scanning, every day

Six scanners run every day across our code, history, dependencies and container image. A scan that finds a problem fails and notifies us.

Dependabot also opens monthly update proposals for our Python, npm, container and CI dependencies, and each one is tested before it is merged.

A few advisories in third-party packages are reviewed and tracked rather than fixed, because the package that depends on them pins an older version. We list each one in the workflow with the reason, and we remove it when the pin lifts.

Credentials and access

Transport and browser protections

Infrastructure and data handling

Report a vulnerability

If you find a security issue, email [email protected] with the subject “Security report”. Please give us reasonable time to fix it before disclosing it publicly, and do not access other customers’ data. Our machine-readable contact is at /.well-known/security.txt.

What we do not claim

BharatStock has not been through a third-party SOC 2 or ISO 27001 audit. The controls above are our own, and each one is something you can check. Automated scanning reduces risk; it does not guarantee that the software is free of vulnerabilities. For the freshness and accuracy of our data, see the Data Trust & Status page.