Skip to main content

​
What this check does

DSALTA samples accessible projects and verifies each has at least one topic (GitLab taxonomy).
This check also runs on 1 other integration — see Code repo should be classified for the full list.
Passes when: Every in-scope repo carries topics or your equivalent DSALTA inventory classification workflow.

​
Why this matters

Unclassified repos complicate operational and compliance risk segmentation.

​
How to fix

Classify code repositories with topics
  1. Open the project in GitLab and go to Settings → General.
  2. Expand Naming, topics, avatar.
  3. In the Topics field, enter one or more classification topics that reflect the project’s criticality and domain (e.g. critical, internal, payments) — the check requires at least one topic per project.
  4. Click Save changes.
  5. Repeat for every project DSALTA reports as unclassified.
  6. (Optional) Record the same classification in DSALTA → Data Library → Inventory using the Tags column (e.g. criticality:critical).
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Data Library → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Data Library → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.