s3scanner
v3.0.3 open-sourceThe section your link pointed to isn't on s3scanner's page any more, so we've brought you to the top.
S3Scanner is a tool to find open S3 buckets in AWS or other cloud providers and scans all bucket permissions to find misconfigurations.
s3scanner --proxy http://10.0.0.1:8080 my-bucket-name s3scanner scan --endpoint-url https://minio.example.com -b test-bucket s3scanner --list -b my-public-bucket
Summary
s3scanner is an open-source, MIT-licensed command-line tool that finds open or misconfigured S3-compatibleS3-compatibleAn object-storage API that mirrors Amazon S3's HTTP interface, so any client or cyber tool written for AWS S3 works unchanged against any compliant storage backend. storage buckets across AWS, GCP, DigitalOcean, DreamHost, Linode, Scaleway, and custom endpoints, checking permissions and enumerating objects rather than just confirming existence. It runs multi-threaded from the terminal or Docker, can save results to Postgres, and pulls bucket names from RabbitMQ for scanning at scale, which suits red teamers and bug bounty hunters doing recon over one-off checks. It's used as a component inside recon frameworks like reconFTW, reNgine, and axiom rather than run standalone by most of its users. First committed in 2017 with 13 contributors, it still saw 6 commits in the past year, though its last release was over 700 days ago.
S3Scanner is a tool to find open S3 buckets in AWS or other cloud providers and scans all bucket permissions to find misconfigurations.
How s3scanner helps
Which of my company's guessable S3 bucket names are actually exposed on the internet right now?
checks each name in a list against AWS and other providers and reports which ones exist and are reachable, rather than just guessing at DNS resolution
Which of the buckets I found can strangers actually read from or write to?
tests each discovered bucket against the full set of permission checks so you see which ones allow anonymous read, write, or ACL access instead of just confirming a bucket exists
What's actually sitting inside a bucket that turned out to be open?
walks the bucket and lists out its objects so you know what data would be exposed, not just that the bucket itself is reachable
Have I already found this exposure before, or is it new since my last scan?
writes each scan's results into Postgres, so past and current findings sit in one place you can diff or query instead of re-reading terminal output
Can my recon pipeline keep discovering and checking bucket names without me feeding them in by hand?
pulls bucket names off a RabbitMQ queue as other tools produce them, checking each one as it arrives so discovery and verification run as one continuous pass at scale
Which bucket names in a huge candidate list are worth a human's attention?
runs checks across many threads at once and can emit JSON, so the output can be piped straight into a filter that keeps only the buckets confirmed to exist
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for s3scanner, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail s3scanner puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
7 entries
No entries match these filters.
- September 20232
- April 20212
- March 20183
Project health
Issue, contributor and maintainer activity in sa7mon/s3scanner, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 ±0 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 33% of issues opened, last 12 months
- Median time to close < 1 day first maintainer reply 0.7 hours
- Open backlog 36 of 149 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 36
- Contributors / month 0
- Commits / month 0
- Stars 3,172
- bugs 67%
- other 33%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.