Candler / Security & coverage
Clear boundaries. Visible limits.
Candler handles private software inventories and security findings. Its design keeps access scoped to teams, limits GitHub permissions, and makes incomplete checks visible. V1 is a limited pilot, with a separate read-only Dependabot preview.
Read-only GitHub access
The V1 GitHub App requests read access to repository contents and metadata. You choose which repositories the App can access. Candler reads supported root lockfiles without running repository code.
The optional Dependabot preview requires separate owner-approved Dependabot alerts read access. Repository selection still applies. Its imported reports remain separate from local finding decisions and send no Candler alerts.
Team access and account protection
Owners, admins, members, and viewers have different permissions. Inventory, findings, and alert destinations belong to a team. Owner accounts require confirmed two-factor authentication.
These are product controls, not a claim of certification or an independent security audit. Final production and accessibility checks are still in progress.
Sensitive connection details
Stored alert webhook settings and selected integration credentials are encrypted by the application. GitHub’s private key is configured in non-public server storage. Logging filters are designed to redact credentials and secret links.
Email, Slack, and Teams deliveries send alert content to the destination your team configures. Consider who can read that destination before adding it. Candler cannot control a recipient’s retention or onward sharing.
What the checks cover
V1 checks supplied WordPress plugin versions and dependencies imported from root composer.lock and package-lock.json files. Wordfence and OSV provide vulnerability records, with CISA KEV used for known-exploitation context.
Candler is not a firewall, malware removal service, penetration test, or proof of exploitability in your application. It does not automatically discover WordPress plugins from a URL.
Freshness and failed checks
Source freshness and scan status matter. A failed, unsupported, or incomplete check stays visible as a gap. Earlier findings can remain in history while their current applicability is unknown.
A clean result means only that no known match was found in the checked source. Continue to use software updates, backups, access controls, and other security practices appropriate to your systems.