Source
Source-code handling, security & compliance — found from sitemap — Codacy
Checked for Codacy on 6 Nov 2026
- Page
- https://docs.codacy.com/security/reports/
- Checked
- 6 Nov 2026, 05:00 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:901ce196a6dc8167fb5c6b6ee13c18af4cbd676fa96f18b658749d792138fdee
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Reports tab Report an error
“The Reports tab of Security and risk management has two reports: Overview: the security posture of your organization, with open findings by severity, scan type distribution, resolution history, and your highest-risk repositories. Remediation: how fast your organization fixes findings of each severity against your SLAs, and how many are overdue right now.”
-
Overview panels Report an error
“The Overview report includes six panels: Open findings overview Scan types distribution Open findings history Activity history Top 10 high-risk repositories Top 10 common security categories”
-
Findings history window Report an error
“The Open findings history graph shows the open findings trends over the past three months, grouped by week and severity.”
-
Activity history Report an error
“The Activity history graph shows weekly counts of open, closed, ignored and unignored findings over the past three months, overlaid on the overall open findings trend.”
-
Remediation severity panels Report an error
“The report has one panel per severity: Critical, High, Medium, and Low. There's no combined figure for all severities, because each severity has its own SLA to compare against.”
-
SLA configuration Report an error
“To configure the SLAs the report uses, click Configure SLAs in the top right-hand corner of the report. This opens the same settings as customizing deadlines on the Findings page.”
-
Remediation window Report an error
“Last 90 days: The mean time to remediate, the on-time share, and the trend use findings closed in the last 90 days. The Open backlog today section uses findings that are open now, whenever they were created.”
-
Remediation counts rules Report an error
“Ignored findings aren't counted: A finding that's ignored when you open the report counts neither as closed nor as open, whatever the reason it was ignored. This applies even if the finding closed before it was ignored.”
-
Remediation sources Report an error
“Every source counts: Findings from Codacy analysis, Jira, penetration testing, app scanning, and container scanning all count, as on the Overview.”
-
SLA retroactive recalc Report an error
“Changing an SLA changes past results. Because the report compares every closed finding against today's SLAs, editing an SLA recalculates the on-time share and the Within SLA or Over SLA status for the whole 90 days.”
-
Overdue buckets Report an error
“90+ days late, 30-90 days late, 1-30 days late: The overdue findings, split by how many days each one is past its deadline.”
-
Trend thresholds Report an error
“The icon doesn't show when: Fewer than 5 findings of that severity closed in the last 90 days. Fewer than 3 findings closed in either the older or the newer half of the 90 days.”
-
Report filters Report an error
“To narrow the report, use the Segments, Repositories, and Scan types filters above the report. The filters apply to every figure, the trend included, and carry over to Open in Findings.”
-
Shareable URL Report an error
“The filters are kept in the page URL, so you can share a filtered report by copying the link.”
Scores citing this record
- The Application Security Engineer Platforms, deployment & administration
- The Engineering Manager Platforms, deployment & administration
- The Lead Developer Platforms, deployment & administration
- The Product Security Officer Platforms, deployment & administration
- The Skeptic Platforms, deployment & administration