Watching software
All docs
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 of software you add to a project gets one. Open the project and its Watches tab to see them, and to change or remove the software you added by hand.
Each project can watch each piece of software once. The same software in two projects is two watches, one per project, each sending to the channels of its own project. For the watches of your plan it counts once.
Kinds of software
- Plugins and themes from the WordPress.org catalog, kept up to date every 15 minutes.
- Premium plugins and themes that are not on WordPress.org. They are in the catalog as soon as a vulnerability is known for them. Once Ladon has checked WordPress.org they are labelled Not on WordPress.org.
- WordPress itself, under core.
- Packages from the registries below.
| Language | Registry | Lockfiles | Manifest | Ranges, for example |
|---|---|---|---|---|
| JavaScript | npm, also with Yarn and pnpm | package-lock.json, npm-shrinkwrap.json, yarn.lock, pnpm-lock.yaml |
package.json |
^4.17.0, ~1.2, >=1.2 <2 |
| PHP | Packagist, as Composer installs it | composer.lock |
composer.json |
^10.0, ~9.5.2, 1.2.* |
| Python | PyPI, with pip, Poetry, uv, Pipenv | poetry.lock, uv.lock, Pipfile.lock, requirements.txt |
pyproject.toml |
~=4.2, >=4.2,<5.0, ==4.* |
| Ruby | RubyGems, with Bundler | Gemfile.lock |
Gemfile |
~> 7.1, >= 1.2, < 2 |
| Rust | crates.io, with Cargo | Cargo.lock |
Cargo.toml |
1.35, ^1.35, ~1.2 |
| Go | Go modules, with Go | go.mod |
>=1.9.0 <2.0.0, ^1.9 |
|
| Java | Maven Central, with Maven, Gradle | gradle.lockfile, pom.xml |
[2.17.1,3.0), (,1.5], [1.2] |
|
| GitHub | public repositories | >=14.0, ^15.1 |
Search for a package by its name, such as @angular/core, laravel/framework or django. A Go module goes by its module path, such as github.com/gin-gonic/gin, and a Java package by groupId:artifactId, such as org.apache.logging.log4j:log4j-core. To watch every package of a repository at once, upload its lockfiles as a project. For packages Ladon also looks up the source repository on GitHub and reads the advisories its maintainers publish there, see GitHub repositories.
Software that WordPress.org closed, for example after a security issue, is labelled Closed on WordPress.org. You can still watch it, but there will be no updates to install. A package its maintainers no longer maintain, such as one deprecated on npm, abandoned on Packagist or with every version yanked on crates.io, is labelled No longer maintained on followed by the registry.
GitHub repositories
Watch a public repository by owner/repo or a link to it. Ladon follows its releases, or its tags when it publishes no releases, and tells you when it is archived. New releases are on by default for repositories, drafts and pre-releases do not count. Advisories come from two places:
- The repository itself. Maintainers can publish a security advisory in their own repository. Ladon reads those directly, often days before GitHub reviews them into the GitHub Advisory Database, and sometimes before there is a CVE. Ladon does this for watched repositories and for the source repository of a package, when its registry points to one on GitHub. When the reviewed copy arrives later, it updates the same vulnerability instead of alerting twice, and
vulnerability.cve_assignedtells you when the CVE number follows. - The GitHub Advisory Database. Actions such as
tj-actions/changed-fileshave their own advisories there, and an advisory for a package also reaches the repository it is built from.
The first time Ladon looks at a repository, advisories older than 30 days are stored without an alert, so you are not flooded with old news. Newer ones alert as usual. Ladon only reads public data here, you connect nothing. A private repository can only be read for its lockfiles, through the GitHub App, see Projects.
Import a list
Adding a hundred plugins one by one takes a while. In a project, choose Add and then Import a list and paste what your sites run, or choose the files. Ladon checks the list before anything is saved and shows each row as In the catalog, Added by slug for premium software, Added by name for packages, Already watched or Skipped, plus how many new watches fit your plan.
Get the list with WP-CLI. Run this in the WordPress folder of a site to get the plugins and themes in one go:
wp plugin list --format=csv; echo '# themes'; wp theme list --format=csv
It prints one line per plugin and theme with its version:
name,status,update,version
woocommerce,active,none,9.3.1
contact-form-7,active,available,6.0.1
# themes
name,status,update,version
astra,active,none,4.8.1
Paste that as it is. WP-CLI output does not say whether it lists plugins or themes, so everything after the # themes line counts as a theme. When you paste only the output of wp theme list, choose Themes on the import page. --format=json and the default table work too. With WP-CLI aliases you get every site at once:
wp @all plugin list --format=csv; echo '# themes'; wp @all theme list --format=csv
A plugin that runs on several sites shows up once, with every version you run. You can also paste one slug per line, such as woocommerce, plugin:gravityforms, theme:astra or core, with the version after a space or @ as in woocommerce@9.3.1, or links to the plugin or theme on WordPress.org.
Every watch starts with the default alerts, every severity and all versions. Ladon does not turn the installed versions into a version constraint, because =2.3.1 is out of date after the next update. The preview uses them to show which of your versions have known vulnerabilities, and whether the latest version fixes them. Tags you add apply to every watch the import creates, for example the client the sites belong to.
When the list has more new rows than your plan has room for, only the first ones are selected. Pick the ones that matter most, or upgrade the plan.
Manifests and lockfiles
Pick the language on the import page and choose its manifest from the table above to watch the packages a project asks for. Each dependency becomes a watch with the range from the file, and dev dependencies are marked. Ranges Ladon cannot read, such as dev-main, mean every version. Git, local and private sources are skipped, plugins from WordPress Packagist become WordPress plugins, and names of private packages never go to a registry. For Python you can also paste the lines of a requirements.txt.
Choose a lockfile instead and the import turns it into a project: Ladon then watches the exact versions, also of the packages your dependencies pull in.
Versions
Choose All versions, or only the versions your sites run. Ladon only alerts when a vulnerability touches the versions you chose.
| You type | It means |
|---|---|
2.3.1 |
Exactly 2.3.1 |
>=2.0 |
2.0 and everything newer |
>=2.0 <3.0 |
From 2.0 up to, but not including, 3.0. A space or a comma means "and" |
2.3.* |
Every 2.3 release, including its betas and release candidates |
!=2.5.0 |
Every version except 2.5.0 |
<1.5 || >=2.0 |
Either range. || means "or" |
The operators are =, !=, <, <=, > and >=. A constraint can be up to 255 characters and 32 parts. For WordPress software caret (^) and tilde (~) are refused on purpose, because tools disagree on what they mean. Packages do use them, see below.
Versions are compared the way WordPress and PHP compare them: 2.3 equals 2.3.0, and 2.3.0-beta1 comes before 2.3.0-rc1, which comes before 2.3.0. The form shows what Ladon understood before you save.
Packages
For packages you type the range the way the manifest of that language writes it, so caret, tilde and the other operators of the ecosystem work here. The table above has examples. npm, Rust and Go versions are compared as SemVer, PHP versions the way Composer does, Python versions as PEP 440, Ruby versions the way RubyGems does and Java versions the way Maven does. Go has no ranges of its own, so Go ranges are written like npm ranges, such as >=1.9.0 <2.0.0. Java ranges use the Maven notation, such as [2.17.1,3.0), (,1.5] or [1.2], and plain operators such as >=2.17.1 work too.
What you hear about
Which alerts you get is decided by the channels of the project, each with its own event types and severity filter. The watches a project makes for its lockfiles, the software you add to a project and its common software have no alert settings of their own.
A watch you make by hand with Add and Watch software, or through the API, keeps its own alert settings on top of those of the channel. Per watch you switch event types on or off. By default you get new vulnerabilities, changes to them, withdrawn vulnerabilities, fixed versions that are released, vulnerabilities that are exploited in the wild or get a public exploit, and malicious versions of npm packages. All types are explained in Events and payloads.
Severity
A watch you make by hand or through the API, and every channel, has a severity filter:
- Every severity: all alerts.
- Pick levels: any combination of Critical, High, Medium, Low and No score.
- CVSS range: a minimum and maximum score for CVSS 3.1 or 4.0. Scores in CVSS 3.0 count as 3.1.
Some findings have no real security impact, such as a missing nonce on a harmless action. They are marked as informational and are off by default. On a watch you made by hand, switch on Include informational findings to get them too.
Tags
Give a watch up to 10 tags, for example the client it belongs to or the environment it runs in: client-acme, production. Tags use lowercase letters, digits, dots, dashes and underscores, start with a letter or digit and are at most 32 characters. Ladon stores them in lowercase.
A channel can take only the alerts of watches with a certain tag, see Channels. Without a tag filter a channel gets the alerts of every watch of its project, so tags change nothing until you use them in a channel.
Pausing
Pause a watch to stop its alerts without losing the settings. A paused watch does not count towards your plan, but resuming it needs a free place. See Plans and limits.
Vulnerability pages
Every alert links to a page with the full details: the description, affected and fixed versions, the first download that contains the fix, CVSS and CWE, whether the CVE is on CISA's list of exploited vulnerabilities, its EPSS score, references, and which watches in your teams are affected. The CVE number opens its own page in Ladon. These pages are public, so anyone who gets an alert can open them. Signed-in members also see their own watches.