Skip to content

Add support for fetching data from api.shodan.io to handle rate limits - #35

Open
dylan1501 wants to merge 8 commits into
s0md3v:mainfrom
dylan1501:main
Open

Add support for fetching data from api.shodan.io to handle rate limits#35
dylan1501 wants to merge 8 commits into
s0md3v:mainfrom
dylan1501:main

Conversation

@dylan1501

Copy link
Copy Markdown

No description provided.

donaldo111 and others added 8 commits August 6, 2026 11:13
*Total -- 39.52kb -> 27.54kb (30.32%)

/static/smap-demo.png -- 34.50kb -> 23.52kb (31.82%)
/static/smap-logo.png -- 5.02kb -> 4.02kb (19.97%)

Signed-off-by: ImgBotApp <ImgBotHelp@gmail.com>
Updated GitHub Actions workflow for Go CI to use newer action versions and improved caching.
[ImgBot] Optimize images
Renames the go.mod module path and all internal imports from
s0md3v/smap to dylan1501/smap so `go install` works against this
fork, and updates README badges/links to match.
--concurrency only bounds worker count, not request pacing, so a
single worker could still blow past Shodan's ~1 req/sec API limit
and silently drop hosts on 429. Add a shared rate limiter (default
1 req/sec, tunable with --shodan-rate) plus a few retries on 429
before giving up on a host.
GitHub's API can lag behind a just-pushed tag ref by a few seconds.
When GoReleaser calls CreateRelease before the tag has propagated,
GitHub silently creates the release under an auto-generated
"untagged-<sha>" tag instead of the real one, leaving the intended
release empty (this happened to the 0.3.1 release). A short sleep
before the GoReleaser step gives the tag time to settle first.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants