⚠ Settings
?
Logout

Why this page exists

NoMoreJoel runs advisory security scans using well-known open-source tools. Scans execute on the control plane (after deploy, daily, or on demand) — we invoke them as separate processes, not as libraries bundled into your application containers. Your servers only run Syft once per release to list the packages in each image; vulnerability matching happens on the control plane.

Security scanning tools

Shown on Security per application
ToolLicenseWhat it checksProject
Gitleaks
Tier-L · Secrets
MIT Detects hardcoded secrets, API keys, and private keys in git repositories after deploy or manual scan. GitHub ↗
OSV-Scanner
Tier-L · Dependencies
Apache-2.0 Matches dependency lockfiles and manifests against the OSV vulnerability database. GitHub ↗
Guarddog
Tier-L · Supply chain
Apache-2.0 Flags suspicious or malicious patterns in PyPI/npm packages in your repo. GitHub ↗
Hadolint
Tier-L · Dockerfile
GPL-3.0 Lints Dockerfiles for security best practices (subprocess only — not linked as a library). GitHub ↗
Syft
SBOM
Apache-2.0 Lists every package in a release's images once per deploy (ephemeral container on your server); the SBOM is stored on the control plane. GitHub ↗
Grype
Image vulnerabilities
Apache-2.0 Matches stored SBOMs against known CVEs on the control plane — on each release and again after each daily advisory update. GitHub ↗

GPL & subprocess isolation

Hadolint is GPL-3.0. We run it only as a separate subprocess on our infrastructure — never imported as a library into the product. GPL tools are never installed on tenant servers.

Route & runtime checks

HTTPS/TLS route probes use Python ssl (PSF license) and the cryptography library (Apache-2.0/BSD). These verify certificates and response headers from the control plane — they do not modify your edge configuration.

Full notices

A machine-readable copy lives in the repository as THIRD_PARTY_NOTICES.md for compliance and audits.

Back to Security