01
Create a read-only credential
Create the credential in SonarCloud with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
Read-only checks on SonarCloud verify your code-quality control is real: quality gates pass on your projects, and organization access is reviewable.
4 read-only checks, run on a schedule. Each failure becomes a finding linked to a control — every check is listed, none are “coming soon”.
Confirms the user token is valid by calling the authentication-validation endpoint. Fails if SonarCloud reports the credentials as not valid.
token-connectivity
Fails if the project's quality-gate status is not OK (i.e. WARN, ERROR, or NONE). A missing or unreadable status is treated as a failure (fail-closed).
quality-gate-passing
Org-scope sanity check: fails if the token is not a member of any organization, which would flag a mis-scoped or orphaned token.
organization-reachable
Access-governance check: fails if the organization has no user groups defined, indicating access is not managed through groups. This is an existence check, so a single read is sufficient.
user-groups-configured
Bring your current platform's test list — we'll map it against these checks, gap by gap
Setup is minutes, not a migration project — and every step stays on your side
Create the credential in SonarCloud with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
The first run starts right after connecting, then repeats on a schedule. Results are timestamped, so your evidence has a history, not a snapshot.
Passing results attach as evidence to the controls they support; failures become findings you triage. When the audit comes, the proof is already connected.
Open any page for its full check register.
You create and scope every credential yourself, and you can revoke it at any time. Checks only read; results and evidence are stored in Switzerland and stay exportable.
Yes. The checks authenticate with a credential you create and scope yourself, and only ever read configuration. devguard holds no write access to SonarCloud and remediates nothing silently.
A failed check becomes a finding linked to the control it supports, with the evidence attached. You decide the treatment — nothing pages your engineers and nothing is auto-remediated.
Checks run from Swiss infrastructure, and results and evidence are stored in Switzerland. Everything is exportable — your evidence stays yours.
20 minutes on how you run certification today. Bring your current test or control list and we'll map it against these checks — honestly, gap by gap.