← Changelog
NewAuditor

Secret scanning, dependency vulnerabilities, and Python and Go checks in static analysis

Thorough reviews now scan the changed files for secrets with gitleaks, look the package versions a changed lockfile adds up in OSV, and check Python with Ruff and mypy and Go with go vet and staticcheck, next to the type checker, ESLint and Semgrep they already ran. Every finding is on a line the pull request added, names its tool and rule, and can be turned off like any static rule. Until now the lockfile was never read, a pasted API key was found only if the deep review happened to notice it, and Python and Go had no checker.

A secret is a High finding on its line, named by gitleaks's rule, with the kind of secret and what to do, never the value. The repository's .gitleaks.toml and .gitleaksignore apply, except for a pull request from a fork, which gets the default rules.

A new version with a known vulnerability is one finding on the lockfile line that pins it, at the advisory's severity, with the advisories and the nearest fixed version. pnpm, npm, Yarn, Poetry, uv, requirements.txt, Pipfile, Bundler, Go, Cargo and Composer lockfiles are read; versions the base branch already pinned are left alone. The lookup runs from Auditor's own workers, with no sandbox.

Ruff runs with the repository's settings or its defaults; mypy only when the repository has a mypy config, with unresolved imports ignored. go vet and staticcheck run for a Go module at the repository root. RuboCop isn't in this release: the sandbox image has no Ruby and can't install one yet.

More in Static analysis.