prowler

Assess AWS, Azure, and GCP security configurations

prowler-cloud/prowler · Cloud Security · scanned 5.47.0 (released 2026-10-29) · commit 555a4cc46990 · 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

no change.

Known vulnerabilities (87)

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.

Second opinion: OSV-Scanner

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

Release integrity

Verdict: no release files.

• 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 prowler-cloud/prowler's own GitHub Actions workflows.

Repository security (OpenSSF Scorecard)

No Scorecard result yet (the project is not in the OpenSSF public dataset; 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)

34 potential issues in 62 workflow files at this release: 1 high, 0 medium, 32 low severity (medium or high confidence only). Each is a pattern to review, not a confirmed vulnerability.

Dependencies (2034)

By ecosystem: npm 1447, pypi 525, github 56, unknown 6.

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