HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
smicallef
spiderfoot
Python2013–2026
smicallef / spiderfoot

spiderfoot

SpiderFoot automates OSINT for threat intelligence and mapping your attack surface.

Security & Privacy
Explore on GitHubRead Hacker News discussions
6Distinct people
7Mentions
0Explicit recommenders
24.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

SpiderFoot automates OSINT for threat intelligence and mapping your attack surface.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year7 dated mentions

Observed mentions: 2013-05-20 20:23:16 UTC to 2026-01-12 20:28:47 UTC.

0122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC101
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC110
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC110
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC211
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

7 sources
redoubt·Jul 5, 2024
<pre><code> What do you mean by "not in working condition". I use it frequently and it just works. </code></pre> Some would disagree with that statement: https://github.com/smicallef/spiderfoot/issues <pre><code> The little development on the project is probably due to it's age. </code></pre> How so? Even the most feature complete software is in need of regular maintenance to assure compatability with new versions of dependencies and OS. Such maintenance would appear to have stagnated since 2022, looking at the commit history.
In SpiderFoot automates OSINT for threat intelligence
cims·Feb 10, 2022Submission

Show HN: Lessons learned from my 10 year open source project

I've been developing SpiderFoot (an OSINT/recon tool) for 10 years now, so wanted to share my story and try to distill some lessons learned in the hope they might be helpful to others here who might be considering writing/open-sourcing their own tools. Here's the post: https://medium.com/@micallst/lessons-learned-from-my-10-year-open-source-project-4… And the repo if you want to check it out: https://github.com/smicallef/spiderfoot -- TL;DR version of lessons from the post.. Lesson 1: Writing open source software can be very rewarding in ways you can’t predict Lesson 2: Be in it for the long haul Lesson 3: Ship it and ship regularly Lesson 4: Have broad, open-ended goals Lesson 5: If you care enough, you’ll find the time Lesson 6: No one cares about your unit test coverage Lesson 7: There’s no shame in marketing Lesson 8: Clear
Read the rest
it with your employer Lesson 9: Foster community Lesson 10: Keep it enjoyable -- I hope you find it useful and inspires some of you to get your project out there! Feel free to ask me any questions here and I'll do my best to answer.
7 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.