l3montree-dev / l3montree-dev/devguard
Strange behavior of Risk counter and Badges
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
If you have open dependency risks in a project those are counted on the dashboard and in the badges.
Now once I accept a risk - the risk is closed and removed from dashboard and badge.
Once I close all open issues, devguard again adds the closed ones which are accepted (I think it skipps the false positive ones).
Some minutes later (maybe 10 or 15) DevGuard switches to an all-green Badge and a clean Dashboard
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported sequence in the dashboard and badges: accept a dependency risk, close all remaining open issues, and observe the result after 10–15 minutes. Trace how accepted and false-positive risks are counted and refreshed; done means accepted risks stay excluded and the dashboard and badge consistently become clean and all-green.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100