#3609 Issue open: Code scanning errors from Codacy¶

Labels: cleanup, discuss / RFC, ReaR Project

jsmeix opened issue at 2026-05-21 09:02:¶

Currently we have

(1)
https://github.com/rear/rear/security
shows Code scanning configuration error
with a link that leads to
https://github.com/rear/rear/security/code-scanning/tools/Checkov%20(reported%20by%20Codacy)/status
which has a link that leads to
https://github.com/rear/rear/security/code-scanning/tools/Checkov%20(reported%20by%20Codacy)/status/configurations/actions-FZTWS5DIOVRC653POJVWM3DPO5ZS6Y3PMRQWG6JOPFWWY
which has a link that leads to
https://github.com/rear/rear/security/code-scanning/tools/Checkov%20(reported%20by%20Codacy)/status/configurations/actions-FZTWS5DIOVRC653POJVWM3DPO5ZS6Y3PMRQWG6JOPFWWY/5bbcd389693f5131c62c0fc48aebb23ca1242ab086c690b6f380fcc4f4885ab4
where I fail to make sense of what that actually means
but as far as I see all that belongs to Codacy.

(2)
https://github.com/rear/rear/security
shows the link Code scanning (5000+) which leads to
https://github.com/rear/rear/security/code-scanning
where 5013 open entries are listed,
all dated Jun 1 2023 and
all reported by Codacy (click on Tool to see that)

We should try to get rid of that old and outdated stuff.
But I don't know how one could do that for 5000+ items
with reasonable effort.

In general I wonder if Codacy is actually helpful in practice?

---

[Export of Github issue for rear/rear.]