Docs
Everything about watching software, channels, webhooks, the API and the payload of every event.
Guides
- Getting started Ladon alerts your team when a vulnerability affects software you run: WordPress core, plugins and themes, open-source packages and public GitHub repositories. T...
- Watching software A watch tells Ladon which software a project runs and which versions. Watches live in your projects: every package in the lockfiles of a project and every piece...
- Projects and lockfiles A project is a repository that Ladon knows by its lockfiles. Upload them, or let Ladon read them from the GitHub repository, and Ladon watches every package in...
- CVE rules Watches are about software you run. A rule is about the whole stream of new CVEs, also for software Ladon does not know. Ladon reads every CVE from the CVE List...
- Channels Channels decide where the alerts of a project go: email addresses, your own webhook endpoint, Slack, Discord or Microsoft Teams. A project can have several chan...
Developers
- Events and payloads Every alert is an event. This page lists all event types and what they contain. Email and webhooks carry the same events, webhooks as JSON.
- Webhooks How Ladon delivers alerts to your endpoint, how to check the signature, and how Ladon reacts to your answers. Ladon follows the Standard Webhooks specification,...
- API With the Ladon API you search the catalog, manage watches, projects and channels, read the delivery log and poll for events. Everything is JSON over HTTPS. Ever...
Account
- Teams and security Everything in Ladon belongs to a team. Inside a team, watches, CVE rules, alerts, channels and sites belong to a project. The team keeps the projects, the brand...
- Plans and limits Each team has a plan, and its limits count for all projects of the team together. The plan decides how many watches, projects, CVE rules and channels can be act...
- FAQ Short answers to common questions. Something missing? Mail support@hackindex.io and we will add it here.