HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
neuromancer
sea
HISTORICAL RECORD2013–2013
neuromancer / sea · Not publicly available

sea

Discover this repository through its Hacker News conversations.

2Distinct people
4Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

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, 3:56:07 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 week4 dated mentions

Observed mentions: 2013-04-12 02:18:48 UTC to 2013-09-28 14:26:15 UTC. Weeks start Monday, UTC.

012013-04-08 00:00:00 UTC to 2013-04-15 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsApr 82013-04-15 00:00:00 UTC to 2013-04-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-04-22 00:00:00 UTC to 2013-04-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-04-29 00:00:00 UTC to 2013-05-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-05-06 00:00:00 UTC to 2013-05-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-05-13 00:00:00 UTC to 2013-05-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-05-20 00:00:00 UTC to 2013-05-27 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2013-05-27 00:00:00 UTC to 2013-06-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-03 00:00:00 UTC to 2013-06-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-10 00:00:00 UTC to 2013-06-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-17 00:00:00 UTC to 2013-06-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-24 00:00:00 UTC to 2013-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-01 00:00:00 UTC to 2013-07-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 12013-07-08 00:00:00 UTC to 2013-07-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-15 00:00:00 UTC to 2013-07-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-22 00:00:00 UTC to 2013-07-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-29 00:00:00 UTC to 2013-08-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-08-05 00:00:00 UTC to 2013-08-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-08-12 00:00:00 UTC to 2013-08-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-08-19 00:00:00 UTC to 2013-08-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-08-26 00:00:00 UTC to 2013-09-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-02 00:00:00 UTC to 2013-09-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-09 00:00:00 UTC to 2013-09-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-16 00:00:00 UTC to 2013-09-23 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2013-09-23 00:00:00 UTC to 2013-09-30 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsSep 23

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
Apr 82013-04-08 00:00:00 UTC2013-04-15 00:00:00 UTC110
Apr 152013-04-15 00:00:00 UTC2013-04-22 00:00:00 UTC000
Apr 222013-04-22 00:00:00 UTC2013-04-29 00:00:00 UTC000
Apr 292013-04-29 00:00:00 UTC2013-05-06 00:00:00 UTC000
May 62013-05-06 00:00:00 UTC2013-05-13 00:00:00 UTC000
May 132013-05-13 00:00:00 UTC2013-05-20 00:00:00 UTC000
May 202013-05-20 00:00:00 UTC2013-05-27 00:00:00 UTC110
May 272013-05-27 00:00:00 UTC2013-06-03 00:00:00 UTC000
Jun 32013-06-03 00:00:00 UTC2013-06-10 00:00:00 UTC000
Jun 102013-06-10 00:00:00 UTC2013-06-17 00:00:00 UTC000
Jun 172013-06-17 00:00:00 UTC2013-06-24 00:00:00 UTC000
Jun 242013-06-24 00:00:00 UTC2013-07-01 00:00:00 UTC000
Jul 12013-07-01 00:00:00 UTC2013-07-08 00:00:00 UTC000
Jul 82013-07-08 00:00:00 UTC2013-07-15 00:00:00 UTC000
Jul 152013-07-15 00:00:00 UTC2013-07-22 00:00:00 UTC000
Jul 222013-07-22 00:00:00 UTC2013-07-29 00:00:00 UTC000
Jul 292013-07-29 00:00:00 UTC2013-08-05 00:00:00 UTC000
Aug 52013-08-05 00:00:00 UTC2013-08-12 00:00:00 UTC000
Aug 122013-08-12 00:00:00 UTC2013-08-19 00:00:00 UTC000
Aug 192013-08-19 00:00:00 UTC2013-08-26 00:00:00 UTC000
Aug 262013-08-26 00:00:00 UTC2013-09-02 00:00:00 UTC000
Sep 22013-09-02 00:00:00 UTC2013-09-09 00:00:00 UTC000
Sep 92013-09-09 00:00:00 UTC2013-09-16 00:00:00 UTC000
Sep 162013-09-16 00:00:00 UTC2013-09-23 00:00:00 UTC101
Sep 232013-09-23 00:00:00 UTC2013-09-30 00:00:00 UTC110

What Hacker News says

4 sources
galapago·Apr 12, 2013Submission

Show HN: An opensource tool for assisted exploit generation on binary programs

Today we are opensourcing an early version of our tool called "Symbolic Exploit Assistant" (SEA) for assisted exploit generation and asking for help/collaboration from the community to expand and improve it. In a few words, this tool starts with a path in a disassembled binary represented with an abstract intermediate language (we start supporting REIL) to generate and solve SMT constraints according to the user request. If the solver finds a solution, the values for the input variables can be used to exploit the path of the program selected. Of course, SEA is not state of the art but a few examples from Gera's Insecure Programming can be "solved". We tried to look for other open source and public tools like SEA, but we couldn't find any. We believe that there should be completely open tools that help people to find vulnerabilities easier
Read the rest
and quicker. We don't like the idea that only some companies and governments have access to such tools. This is a very small step in the direction of the democratisation of the access to exploitation tools. Finally, we ask the community for help to do research, development and implementation of SEA in order to build a tool to perform binary analysis. The code and some documentation is available in: https://github.com/neuromancer/sea
4 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.