Security can find a lot: one vulnerable package reported by six advisories, a secret scanner matching the same example password in fifty documentation files. You don't decide on findings one by one. Security sorts them into decisions: every open finding that one answer settles. CoRoid has already answered each one. You check its answers, change the ones that are wrong, and apply them a pile at a time.
Decisions is a tab of Security, between Overview and Projects. Its count is how many decisions are urgent.
What makes one decision
- A package, across all your projects: "hono → 4.13.16 in 2 projects" is one decision, however many advisories the upgrade fixes.
- A folder of test code or tooling: everything under
e2e/or a coding tool's.opencode/, whatever kind of finding it is and whatever severity the scanner gave it. - Examples of one kind: credentials written down on purpose in the
documentation, words in translation catalogues, seed data,
.examplefiles. - A rule in one service: "Broken access control in apps/api-admin". Claims that no independent check confirmed are a decision of their own, apart from confirmed findings.
- A secret rule in a project's code.
A finding whose fix is already under way is in no decision. It is listed once under the piles ("CoRoid is already on 2 more") and comes back only if the fix fails. A finding an exception hides is in no decision either.
Three piles
- Urgent: exploited anywhere, or critical or past its fix date in what you deploy. Work through it first.
- Should do: in what you deploy, not past its fix date. It can wait a few days.
- Clean-up: test code, tooling, examples and low claims, whatever their severity. Mostly noise, answered in bulk.
Each pile shows how many decisions are left, about how long they take, and a bar of what you answered today.
CoRoid's answer
Every decision carries CoRoid's answer, with Sure or Likely and one line of why. Open a decision to read the whole reason, where its findings are, and every answer with what it does.
When only a person can tell, for example whether a credential in your code is real, the decision has no answer and says Needs your call. Apply passes it by until you choose.
Judging it from the code
A decision about a credential or a code finding opens with Where it is: each place, with the lines around it as they were in the commit the scan saw it in, the flagged line marked, and for a GitHub repository Open on GitHub, which opens that line in that commit. You don't need an editor or a checkout to decide.
The credential itself never leaves CoRoid's copy of your repository. Every value that looks like a credential on the lines shown is hidden, and Security tells you only its length and how it looks:
- a common default word, the kind a local setup uses (
changeme,postgres); - random-looking, as a real key or password usually is;
- readable text, such as a passphrase.
What decides most cases stays visible: the variable it is assigned to, the
host in a connection string, whether the line is a comment, and references
such as ${DB_PASSWORD} that hold no value.
When a file was deleted after the scan found the credential, the place says so. Deleting a file does not take a credential out of the repository's history: anyone who can read the repository can still find it in the earlier commits. If it is real, rotate it.
| Answer | What it does |
|---|---|
| Start a fix | Files one task for the decision's findings in each project. The fix comes back as a pull request. |
| Check, then fix what is real | The same task for claims: it checks each claim first, fixes the real ones and leaves a note on the rest. |
| Open the upgrade | Opens the upgrade as fix work, one pull request per project. |
| Ignore the folder | Findings under that folder stop counting, now and in later scans. You can undo it. |
| Not a secret | Closes the findings, and the secret scan learns from your answer. |
| Not a problem… | Closes them as false positives, with your reason in their history. |
| Accept for 90 days | Hides them for 90 days, or until their severity rises. |
| Yes, rotate it | Files the rotation checklist. The finding closes when you confirm the old value no longer works. |
| Yes, already rotated | Closes them with your confirmation. |
| Hand to an admin… | Moves it to another owner or admin's list, with your note. |
| Skip for today | It comes back tomorrow, in the same place. |
When you change an answer, Security offers the same answer for the decisions like it: "1 more decision looks like this… Same answer".
Applying a pile
Apply applies every answer in the pile that is ready. A message says what work started (it shows in the Factory) and offers Undo. Answered today lists your answers. You can take back those whose records allow it: exceptions, verdicts, skips and handovers. Started work stops in the Factory, not here.
When Urgent is done, Security says how many decisions are left and how many of them are past their fix date, then offers Stop for today or Keep going.
The keyboard works too: ↑ and ↓ move between decisions, Enter opens one, 1 to 9 choose an answer, and ⌘ Enter applies.
In the Factory
The Factory's Needs you holds one Security row while a decision is urgent: "5 urgent decisions · about 2 min · 32 in all". Start opens Decisions. A decision that cannot wait has a row of its own: an exploited package, a confirmed critical finding, or a credential a person confirmed is real, in what you deploy.
Once nothing is urgent, the row leaves Needs you, and one line says how many decisions can wait for your next session.
Who answers
Owners and admins answer decisions. Members read them and their evidence.
CoRoid's MCP and Chat tools list the same decisions (list_security_needs).
See Security from MCP and Chat.