Making it usable
Blast radius
Two halves of the same question. Access is who can reach a repository. Software is what is inside one.
The other half
Blast radius has a Software tab, built from the bill of materials rather than from the findings, so a package with no advisory against it still has a row and a name typed into the box comes back with every repository and branch holding it. Software inventory has a page of its own, because it answers a different question from everything below.
On the finding
What the repository holds, the application it belongs to, both owners, whether the default branch is protected, and who can push to it with outside collaborators counted separately. The same credential in a payment system and a brochure site are not the same problem.
Where the answers come from
Each answer says whether it was set on the repository or inherited from the account. "Nobody has said" and "somebody said, for the whole account" are different states and showing them the same way asserts something nobody did.
Tagging in bulk
The whole set exports to a spreadsheet and comes back, because tagging two hundred repositories through a form is data entry and the answers usually already live in an asset list. An empty cell leaves a value alone; a dash clears it; a repository the scanner has never seen is reported rather than created.
What it does not do
The access inventory needs a credential that can read organization membership. Without one it shows what it can and says so.
Every feature page carries one of those. The comparison page scores the same ground against five products people pay for, including the rows that go against us.