prowler

prowler-cloud/prowler

This repo hosts Prowler OSS (CLI and Local Server). Prowler is the world’s most widely used open-source cloud security platform that automates security and compliance across any cloud environment for Humans and AI Agents.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
11 Nov 2026
today
Ship score
100/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 14,890 → 15,201 (29 Sep – 10 Nov 2026)
+186 stars in the 28 days to 10 Nov 2026

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
15.2K
Forks
2.5K
Open issues
482
Watchers
128
Primary language
Python
Created
24 Aug 2016
Owner
prowler-cloud · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 112 startups in the directory ship primarily in Python.

Topics

#aws#azure#cis-benchmark#cloud#cloudsecurity#compliance#cspm#devsecops#forensics#gcp#gdpr#hacktoberfest#hardening#iam#multi-cloud#python#security#security-audit#security-hardening#security-tools

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 22 Sep 2026 — os_startup 94%, self-hostable 58%, hosted offering 73%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the Sep 2025 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 11 Nov 2026This is the badge for prowler-cloud/prowler, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/prowler-cloud/prowler.svg)](https://ossean.com/prowler-cloud/prowler)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.