# Security guides

> How to keep the code you write or review safe, per kind of contribution.

Source: https://contributors.home-assistant.io/security/guides/

Each guide covers one kind of contribution. They build on [how Home Assistant handles trust](https://contributors.home-assistant.io/security/how-it-works/), so read that first if you have not yet.

- [Secure integrations](https://contributors.home-assistant.io/security/guides/integrations/): credentials, certificates, redaction, admin-only access, webhooks, and file paths.
- [Untrusted content in the frontend](https://contributors.home-assistant.io/security/guides/frontend/): escaping, sanitizing, and safe links.
- [Secure apps](https://contributors.home-assistant.io/security/guides/apps/): what the advisories about apps and the Supervisor teach.
- [Secure companion apps](https://contributors.home-assistant.io/security/guides/companion-apps/): links, exported components, the WebView, and the JavaScript bridge.
- [Dependencies and supply chain](https://contributors.home-assistant.io/security/guides/dependencies/): what Home Assistant asks of a library, and how it checks.
- [Review with security in mind](https://contributors.home-assistant.io/security/guides/reviewing/): what to look for in a pull request, and what to do when you find something.