First Seen
Feb 18, 2026
Last Scanned
Feb 20, 2026
Findings
9
Score
84/100
Findings (9)
Detects conditional execution based on CI environment variables combined with dangerous commands
${{ secrets.GITHUB_TOKEN + node -ePin all dependencies to exact versions with integrity hashes. Use lock files (package-lock.json, poetry.lock) and enable checksum verification in your package manager.
Likely FP if the match is documentation about dependency management best practices rather than actual unpinned dependency declarations.
Detects attempts to access the Docker daemon socket
/var/run/docker.sockBlock access to cloud provider IAM and credential endpoints from agent tools. Implement egress filtering to prevent requests to cloud control plane APIs.
Likely FP if the match is documentation about cloud IAM setup rather than code that programmatically accesses IAM endpoints.
Detects URLs fetched at runtime that control or influence agent behavior without pinning
get --no-verbose --tries=1 --spider http:// + instructionsAvoid loading configuration or behavior-controlling content from runtime URLs. Bundle required configurations locally or pin remote config to versioned, integrity-verified endpoints.
Likely FP if the URL in the match is a documentation link or example URL (e.g., example.com) rather than an actual runtime-fetched configuration endpoint.
Detects system-level package installation via brew, apt, yum, or dnf
apt-get install -y cPin system packages to specific versions where the package manager supports it. Document the exact packages required and prefer containerized environments to avoid system-wide changes.
Likely FP if the match is standard setup documentation listing well-known system packages (e.g., apt install git curl) that are prerequisites.
Detects system-level package installation via brew, apt, yum, or dnf
apt-get install -y pPin system packages to specific versions where the package manager supports it. Document the exact packages required and prefer containerized environments to avoid system-wide changes.
Likely FP if the match is standard setup documentation listing well-known system packages (e.g., apt install git curl) that are prerequisites.
Detects GitHub Actions references using mutable branch names instead of pinned commit SHAs or tags
uses: aquasecurity/trivy-action@masterVerify that build scripts and Makefiles do not download or run code from untrusted sources. Audit all build steps and pin any external tools used during the build process.
Likely FP if the build script only runs standard toolchain commands (e.g., cargo build, go build) without downloading external resources.
Detects system-level package installation via brew, apt, yum, or dnf
apt-get install -y pPin system packages to specific versions where the package manager supports it. Document the exact packages required and prefer containerized environments to avoid system-wide changes.
Likely FP if the match is standard setup documentation listing well-known system packages (e.g., apt install git curl) that are prerequisites.
Detects system-level package installation via brew, apt, yum, or dnf
apt-get install -y pPin system packages to specific versions where the package manager supports it. Document the exact packages required and prefer containerized environments to avoid system-wide changes.
Likely FP if the match is standard setup documentation listing well-known system packages (e.g., apt install git curl) that are prerequisites.
Detects system-level package installation via brew, apt, yum, or dnf
apt-get install -y pPin system packages to specific versions where the package manager supports it. Document the exact packages required and prefer containerized environments to avoid system-wide changes.
Likely FP if the match is standard setup documentation listing well-known system packages (e.g., apt install git curl) that are prerequisites.