checkov

Scan cloud infrastructure configurations

bridgecrewio/checkov · Infrastructure as Code Security · scanned 3.4.0 (released 2026-10-28) · commit 9504d068f841 · last scan 2026-11-02

The scan method changed on 2026-11-02. npm development dependencies and npm-shrinkwrap.json are now scanned; matches on GitHub Actions referenced by a moving tag and on npm packages the repository defines itself are no longer counted; directories such as integration-tests and test-fixtures are excluded as fixtures. Most differences from the previous week below come from that change, not from the projects. Details.

Changes since last week

4 resolved.

Resolved advisories (4)

• C GHSA-5xjx-3w67-w9x9 in pypa/gh-action-pypi-publish@v1
• H GHSA-ghm2-rq8q-wrhc in tj-actions/verify-changed-files@v13
• H GHSA-mrrh-fwg8-r2c3 in tj-actions/changed-files@v44
• L GHSA-vxmw-7h4f-hqxh in pypa/gh-action-pypi-publish@v1

Known vulnerabilities (86)

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. OSV: also reported by OSV-Scanner. Released binary: for Go tools, whether govulncheck found the vulnerable code in the shipped Linux binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Select an advisory for every catalog tool it matches. If a match is wrong or does not apply, use Dispute; accepted disputes are annotated here and listed on the corrections page, and the match stays visible.

Not counted: 4 matches (action reference to a moving tag or branch). Neither identifies a version installed from a registry.

Second opinion: OSV-Scanner

OSV-Scanner found 131 advisories in the same files; 59 of Grype's matches are confirmed by it (marked ✓ above). 48 advisories were reported only by OSV-Scanner.

Release integrity

Verdict: no checksums or signatures for checkov_linux_X86_64.zip. The download matches GitHub's recorded digest.

• Checksums file: no
• Signatures: no
• SLSA provenance: no
• SBOM published with the release: no

Verified means a signature, provenance, or attestation was checked against an identity in bridgecrewio/checkov's own GitHub Actions workflows.

Repository security (OpenSSF Scorecard)

No Scorecard result yet (the OpenSSF public dataset entry is 1435 days old (limit 30); the Scorecard CLI fallback was skipped because this shard's weekly budget was used). Results are added as the weekly budget allows.

GitHub Actions workflow audit (zizmor)

18 potential issues in 10 workflow files at this release: 10 high, 4 medium, 3 low severity (medium or high confidence only). Each is a pattern to review, not a confirmed vulnerability.

Dependencies (133)

By ecosystem: pypi 102, github 30, unknown 1.

Licenses (as declared in the SBOM): unknown 133.

History

SBOM minimum elements

Scored by sbomlyze on the generated source SBOM. A source SBOM usually lacks supplier and hash data, so these scores mostly reflect what the project's manifests declare.

Evidence

Downloads for this week: CycloneDX SBOM · Grype report

Permanent copy of the raw SBOM, Grype, OSV-Scanner, and govulncheck output and release checks: release report-2026-11-02, folder supply-chain-shard-*/bridgecrewio__checkov/.

Full JSON for this project · Atom feed of weekly changes

Badges

shields.io endpoints refreshed with each weekly scan. They report this week's result for the latest release, nothing more.

[![release verification](https://img.shields.io/endpoint?url=https%3A%2F%2Frezmoss.github.io%2Fawesome-security-pipeline%2Fbadges%2Fbridgecrewio%2Fcheckov%2Frelease.json)](https://rezmoss.github.io/awesome-security-pipeline/projects/bridgecrewio/checkov/index.html)

How this report is made

Every Sunday a GitHub Actions workflow resolves each catalog tool to its latest release and runs the checks below. Every tool is installed from its own latest release and verified against its published checksum or digest. Nothing from the scanned projects is built or executed; release binaries are analyzed as files.