Solutions
Solutions
One server holds the score history of every repo you onboard. Who runs it changes; the setup does not.
One developer, many repos
Track every side project and app from one dashboard instead of a report per CI run.
- One server and one basicAuth pair for every repo
- Registration per repo in a single command
- Build retention keeps a small database small
Agencies with client sites
Score the sites you build in CI, and the ones with no pipeline through PSI collection.
- Own-build audits for sites you build and deploy
- PSI collection for Client sites without CI
- Live audits of the deployed URL in a separate Project
Teams with signed-in apps
Audit dashboards and account pages, not only the marketing pages.
- Credential login in dev and staging
- Session injection in production behind CAPTCHA or Turnstile
- Scores posted on each pull request with GITHUB_TOKEN