Back

Audit a GitHub repo for security and risky dependencies

A ranked findings table of vulnerable packages, exposed secrets, and license risks

Engineering
Prompt

Audit this GitHub repo for security issues and compromised dependencies: [repo URL, e.g. a public repo or a private one I can access]. Scope: [audit scope, e.g. main branch, production dependencies only]. Open the manifests and lockfiles (package.json, package-lock.json, or the equivalents for its language). For each direct dependency, compare the pinned version to the latest on npmjs.com and check the GitHub Advisory Database. Flag known vulnerabilities, abandoned packages, recent maintainer changes, typosquat-looking names, and install scripts. Then check the repo itself: committed secrets or keys, GitHub Actions workflows with unpinned actions or broad token permissions, and license conflicts. If I have access, include open Dependabot and code scanning alerts. If I paste [audit output, e.g. npm audit results], use it. Don't open issues, pull requests, or change settings. Hand back a table: finding, file or package, severity, evidence link, suggested fix. Rank by severity and list anything you couldn't check.

Works withgithub.comnpmjs.com