sn0int
v0.24.3 open-sourceThe section your link pointed to isn't on sn0int's page any more, so we've brought you to the top.
sn0int is a semi-automatic OSINTOSINTOpen-source intelligence, collecting and analyzing information from publicly available sources. Investigators use it to learn about people, infrastructure or threats. framework and package manager that gathers intelligence about a target by processing public information.
GOARCH=riscv64 go build
sn0int run <module>
sn0int run -X http://proxy.example.com:8080 <module>
export SN0INT_WORKSPACE=my_workspace && sn0int scan
sn0int stats
sn0int cal 2020
sn0int cal -TC3
sn0int pkg list --source notifications
sn0int pkg quickstart
mqtt_connect("tcp://broker.example.com:1883")
libsodium_decrypt_secretbox(secret_box_data, key)
exit
quit
lock = ratelimit_throttle(limit=10, interval=60)
with lock:
do_something()
sn0int urls add https://example.com
sn0int ports add 443
sn0int repl
sn0int export workspace.json
sn0int run -t 'where id=1' foo.ki
http_fetch_json("https://api.example.com/data", required_fields=["id", "name"])
sn0int search --new
sn0int noscope
select --paths from structs
sn0int --proxy socks5://127.0.0.1:9050 scan target.com
sn0int help
sn0int selftest --check-all
echo 'example.com' | sn0int --script scan.ki --stdin
sn0int run & sn0int run & wait
sn0int quickstart
sn0int db_select --url 'example.com'
sn0int mod update
Summary
sn0int is an open-source, semi-automatic OSINT framework and package manager, free to use, run from the command line, that gathers public information about a target and maps it into a unified format for follow-up investigation. It targets IT security professionals, bug bounty hunters and law enforcement, along with security awareness trainers, rather than developers or platform teams. Modules handle each investigation type — certificate transparency and passive DNS for subdomains, PGP keyservers for emails, ASNASNAutonomous System Number — a globally unique identifier assigned by regional internet registries to a network operator, letting routing protocols distinguish which organization controls a block of IP addresses. and geoip enrichment, phone number lookups — and run sandboxed, so users can write and publish their own to sn0int's registry instead of submitting pull requests. Its README describes it as heavily inspired by recon-ng and Maltego, though more flexible and fully open source. Development goes back to 2018 with 14 contributors, but there have been no commits in the past year and the last release was over 700 days ago.
sn0int is a semi-automatic OSINT framework and package manager that gathers intelligence about a target by processing public information.
How sn0int helps
What subdomains does a target actually have, beyond what its own DNS records advertise?
pulls certificate transparency logs, passive DNS sources and the Wayback Machine for hostnames tied to the domain and stores every subdomain found under one entity for that target
Which of those subdomains have something publicly reachable on them?
mass resolves the collected subdomains and probes them for live http or https services, sifting the list down to the ones actually worth investigating
Who is behind a given email address or account, and where else do they show up?
checks pgp keyservers and whois for matching emails, searches for the same username or profile across other sites, and links any breach exposures it finds back to that identity
What can be learned about an IP address without touching the target directly?
enriches each collected IP with ASN and geoip data so the address is tied to a network and a rough location before any further probing
What devices and hosts are actually present on a local network segment?
uses passive network techniques such as ARP monitoring to enumerate devices without sending traffic that would alert anything on the network
Has new information appeared since the last time this target was investigated?
modules can be run again on the same scoped entities, and results feed into the same stored dataset so new subdomains, emails or breach hits accumulate alongside what was already found
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 sn0int, 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 sn0int 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
23 entries
No entries match these filters.
- November 20221
- December 20211
- October 20211
- September 20211
- May 20211
- December 20201
- June 20201
- March 20201
- February 20202
- January 20202
- November 20191
- August 20191
- June 20191
- April 20191
- January 20192
- December 20182
- November 20182
- October 20181
Project health
Issue, contributor and maintainer activity in kpcyrd/sn0int, 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 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed 0% of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog 48 of 114 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 48
- Contributors / month 0
- Commits / month 0
- Stars 2,536
- other 100%
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.