Security: 1 code-scanning alert of class MaintainedID [code-scanning class MaintainedID]

[iderex]

Board: yes

Security and quality alerts are worked before any phase, one issue per class of alert (the rule of 2026-09-05 on steinbruch, fleet-wide since 2026-09-06). This is the class MaintainedID from code-scanning, 1 open alert, the highest severity high.

What the class says

Determines if the project is "actively maintained".

The alerts

• alert Record the two normal absences, a slow server and a server that is gone #7, severity high, at no file associated with this alert:1: https://github.com/Flowfin/core/security/code-scanning/7

Done when

• This class stands at zero open alerts on the Security tab: every alert repaired by a change that lands here, or dismissed with a reason written on this issue that names the predicate, pasted from the API rather than clicked.
• The planning issue for this class on the operations tracker, which asks how the class is kept from arriving again, is named here; nothing here waits on it.