Coverage where extensions are published
- Marketplace registries used by VS Code, Cursor, and Windsurf
- Exact-release reports for every monitored version
- No editor plugins required — review happens beside the marketplace
Integrations
Evidence where your team already works.
Guardrails does not ask you to live in another dashboard. Reports reach your inbox, your chat, your tracker, and your terminal — and stay portable everywhere.
Meaningful changes only
- Email alerts when a release gains new capability
- Slack delivery targets, encrypted at rest
- Quiet re-publishes stay silent; behavioral changes do not
Decisions land where the team already works
- Weekly digest of watched-extension changes
- Jira tickets from review decisions
- Shared inbox with assignment and rationale
Analysis on your machine
- GuardRails CLI inspects extensions installed locally
- Portable report bundles move evidence without uploading it
- Import into the browser Reports library when you choose
Records your compliance flow can consume
- Role-aware CSV and JSON audit export
- Immutable scan dossiers with stable links
- Public metrics and inventory endpoints for your own tooling
Build on the same evidence
- Published API endpoints for scans, inventory, and rules
- Report bundles as a stable interchange format
- Webhook-friendly release events for pipeline gates
What integrations do not do
No ambient access. No silent expansion.
- Guardrails never asks for access to your editor, repositories, or source code — the product reviews published releases.
- Delivery targets (Slack, email, Jira) carry notifications out; they never grant Guardrails write access into those systems.
- Local CLI results stay on your machine until you deliberately export a portable report.
Start with one release
Search extensions Check an extension today.
Open a public exact-release report, then wire notifications into the channel your team actually reads.