Security
What an attacker would look for first: credentials, known-vulnerable packages and code that trusts input it should not.
43% of the overall scoreSignals in this suite
- Secret scanning
- Vulnerable dependencies
- Code vulnerabilities
Explore checks & tools
Secret scanning
gitleaksCloud, SaaS and payment provider keys, tokens, passwords and private keys committed to the tree.
Vulnerable dependencies
OSV-ScannerPackages your lockfiles pin, matched against osv.dev — npm, PyPI, Go, crates.io, Maven, RubyGems and more. Malicious packages are critical; actively exploited CVEs (CISA KEV) are ranked up.
Code vulnerabilities
Opengrep · vetkit rulesSelected language-specific rules for injection, unsafe deserialization, weak crypto, disabled TLS checks, SSRF and XSS, plus insecure server, mobile and shell configuration, with CWE references.
Security posture
nativeCommitted .env files, keystores, cloud and Terraform credentials, database dumps, manifests without a lockfile, no SECURITY.md disclosure policy.
Infrastructure & CI/CD
Trivy · zizmorTerraform, CloudFormation, Kubernetes, Helm and Dockerfile misconfigurations; GitHub Actions script injection, over-broad tokens and pwn requests.
Supply chain & outdated software
native · Retire.js · endoflife.dateLockfile injection, risky install scripts, Trojan Source, vendored vulnerable libraries and end-of-life runtimes or base images.
- Secret values are redacted — only a one-way hash tracks a finding across audits
- A repository cannot hide findings with its own scanner config files or inline ignore comments

