Why most audit reports go unread
An automated security report is usually long and mostly wrong. Two hundred warnings, most of them things that cannot happen in your app. A person has to sort the real ones from the noise, and after the third false alarm they stop reading.
The useful audit is short. It lists what is real, shows why, and comes with the fix.
How a Bugstack audit works
Bugstack does autonomous software maintenance. You start an audit from the Security page for one repository.
- It maps the code. It reads the repository at its latest commit and plans which areas to check.
- It hunts. It looks through each area for problems of known kinds.
- It verifies. Each suspected problem goes to a separate check that tries to prove it. What cannot be stood up is dropped or marked as unproven.
- It groups. Findings with one root cause become one case, so you do not get ten reports about the same missing check.
- It starts the fixes. Each case goes into the same path as any other fix: reproduced, fixed, opened as a pull request.
- It reports. You get a page listing what was found, what was proven, what is being fixed, and what Bugstack cannot fix for you, with a guide for those.
You control the depth and the budget
| Choice | What it does |
|---|---|
| Quick | The riskiest areas first. Fastest, and uses the least credit |
| Standard | Every area the audit plans, in two passes. Recommended |
| Deep | More areas and a third pass. Slowest and most thorough |
| Budget | You set how much credit the audit may use. When it reaches the budget it pauses, shows what is done and what is left, and asks before continuing |
Fix pull requests from an audit are limited to a few open at a time per repository, most severe first, so the audit does not flood your review queue.
After the first audit you can run one on only the code that has changed since, or schedule one monthly or every three months.
Your first audit is on us
A workspace’s first security audit comes with $50 of credit from us, separate from the trial’s $50. The audit’s budget is set to that amount. If it needs more to finish, it pauses and asks before using your own credit.
What an audit does not do
- It does not replace a penetration test of your running system. It reads code.
- It does not certify anything. It is not a compliance report.
- It does not rotate secrets or change settings on your host.
How to start
- Sign in with GitHub and start the 14-day trial.
- Install the Bugstack GitHub App on your repository.
- Open the Security page, choose the repository and a depth, and start the audit.
Questions
How is this different from a code scanner?
A scanner matches patterns and reports every match. An audit tries to prove each finding before it tells you, groups findings by root cause, and starts the fix. You get fewer items, and each one is real or clearly marked unproven.
Will it change my code without asking?
Fixes arrive as pull requests. New repositories start on Review, where you merge each one. Changes to sign-in and security code wait for a person by default at every level.
How long does an audit take?
It depends on the size of the repository and the depth you choose. You can leave it running; the report page shows progress and the pull requests appear as they are ready.