HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
glato
emerge
Python2023–2023
glato / emerge

emerge

Emerge is a browser-based interactive codebase and dependency visualization tool for many different programming languages. It supports some basic code quality and graph metrics and provides a simple and intuitive way to explore and analyze a codebase by using graph structures.

2Distinct people
2Mentions
0Explicit recommenders
1.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Emerge is a browser-based interactive codebase and dependency visualization tool for many different programming languages. It supports some basic code quality and graph metrics and provides a simple and intuitive way to explore and analyze a codebase by using graph structures.

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, 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 3-hour interval2 dated mentions

Observed mentions: 2023-04-17 23:07:12 UTC to 2023-04-19 20:55:03 UTC.

012023-04-17 21:00:00 UTC to 2023-04-18 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 17, 21:002023-04-18 00:00:00 UTC to 2023-04-18 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-18 03:00:00 UTC to 2023-04-18 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-18 06:00:00 UTC to 2023-04-18 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-18 09:00:00 UTC to 2023-04-18 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-18 12:00:00 UTC to 2023-04-18 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-18 15:00:00 UTC to 2023-04-18 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-18 18:00:00 UTC to 2023-04-18 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 18, 18:002023-04-18 21:00:00 UTC to 2023-04-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-19 00:00:00 UTC to 2023-04-19 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-19 03:00:00 UTC to 2023-04-19 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-19 06:00:00 UTC to 2023-04-19 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-19 09:00:00 UTC to 2023-04-19 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-19 12:00:00 UTC to 2023-04-19 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-19 15:00:00 UTC to 2023-04-19 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-19 18:00:00 UTC to 2023-04-19 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 19, 18:00

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 17, 21:002023-04-17 21:00:00 UTC2023-04-18 00:00:00 UTC101
Apr 18, 00:002023-04-18 00:00:00 UTC2023-04-18 03:00:00 UTC000
Apr 18, 03:002023-04-18 03:00:00 UTC2023-04-18 06:00:00 UTC000
Apr 18, 06:002023-04-18 06:00:00 UTC2023-04-18 09:00:00 UTC000
Apr 18, 09:002023-04-18 09:00:00 UTC2023-04-18 12:00:00 UTC000
Apr 18, 12:002023-04-18 12:00:00 UTC2023-04-18 15:00:00 UTC000
Apr 18, 15:002023-04-18 15:00:00 UTC2023-04-18 18:00:00 UTC000
Apr 18, 18:002023-04-18 18:00:00 UTC2023-04-18 21:00:00 UTC000
Apr 18, 21:002023-04-18 21:00:00 UTC2023-04-19 00:00:00 UTC000
Apr 19, 00:002023-04-19 00:00:00 UTC2023-04-19 03:00:00 UTC000
Apr 19, 03:002023-04-19 03:00:00 UTC2023-04-19 06:00:00 UTC000
Apr 19, 06:002023-04-19 06:00:00 UTC2023-04-19 09:00:00 UTC000
Apr 19, 09:002023-04-19 09:00:00 UTC2023-04-19 12:00:00 UTC000
Apr 19, 12:002023-04-19 12:00:00 UTC2023-04-19 15:00:00 UTC000
Apr 19, 15:002023-04-19 15:00:00 UTC2023-04-19 18:00:00 UTC000
Apr 19, 18:002023-04-19 18:00:00 UTC2023-04-19 21:00:00 UTC101

What Hacker News says

2 sources
Slightly off topic & very resource intensive diy approach without using an IDE: Take advantage of an editor's use of on disk file as a buffer[0]. Monitor the editor file buffer for changes[1]. Trigger regeneration of a map/graph update & redisplay changes[2] in different non-editor window. Where [2]'s configuration could be done to display editor buffer stats & how relates to other things beyond the current buffer. Selecting / clicking on [2] node displays ctag buffer reference to jump to / sends ctag to named pipe editor monitoring. [0] : https://stackoverflow.com/questions/71822798/what-exactly-ar... [1] : watchdog : https://pypi.org/project/watchdog/ [2] : emerge-vis : https://github.com/glato/emerge
In Ask HN: In-editor visual mind map/graph tool for code?

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.