SystemAudit

Ask Claude "Should I depend on github.com/lukeed/clsx?", "Compare these two libraries" or "Give me a due-diligence read of this repo". SystemAudit gives a security and code-health review of any public GitHub repository: a health score out of 100, the top risks in plain English, how the project is built, and how many potential hardcoded credentials it contains. Works on any public repository, with no sign-in and no account. Private repositories are refused by design: the connector holds no GitHub account access, which keeps it safe to point at any public repository. Scan private ones on systemaudit.dev. Built for the moment before you commit to a codebase: choosing an open-source dependency, running technical due diligence on an investment or acquisition, inheriting a repository, or sanity-checking code an AI tool generated. Three tools: scan_repository: health score, ranked risks, how the project is built, credential counts, and how many files were read out of how many exist. get_architecture: package ecosystem, architecture pattern, language mix, dependency count, circular imports and files nothing else imports. secrets_summary: potential hardcoded credentials and committed environment files, counted by severity. Honest by design. Every answer states how many files were read, so a clean result is never mistaken for a clean repository. The connector returns credential counts by severity only, never a file, line or value; the linked full report on systemaudit.dev shows locations for critical and high findings, as it does for any public repository scan. Your conversation stays yours: the connector receives only the repository you name. No code is executed, no file contents are returned, and we keep the resulting report, not a copy of the repository. Response times: an already-scanned repository answers from its saved result. A first scan reads the repository through the GitHub API, so larger repositories take longer. New scans are rate-limited.