HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dw
csvmonkey
C++2017–2020
dw / csvmonkey

csvmonkey

Header-only vectorized, lazy-decoding, zero-copy CSV file parser

3Distinct people
6Mentions
1Explicit recommenders
102GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Header-only vectorized, lazy-decoding, zero-copy CSV file parser

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

As much as I love SQLite, and while it is open source, it is a single implementation that AFAIK has no published open specification. The only way to read an SQLite file is…

_wmd used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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, 7:02:50 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 year6 dated mentions

Observed mentions: 2017-06-12 17:46:52 UTC to 2020-10-10 13:18:24 UTC.

01232017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020

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
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC303
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 UTC101

What Hacker News says

1 sources
I'm not "making a claim" or inventing a heuristic, you can test this trivially: $ git clone https://....:x-oauth-basic@github.com/dw/csvmonkey.git Cloning into 'csvmonkey'... remote: Counting objects: 340, done. remote: Compressing objects: 100% (27/27), done. remote: Total 340 (delta 19), reused 27 (delta 10), pack-reused 303 Receiving objects: 100% (340/340), 138.93 KiB | 0 bytes/s, done. Resolving deltas: 100% (212/212), done. $ cat csvmonkey/.git/logs/HEAD 0000000000000000000000000000000000000000 c9d566bf167dcf3556008df58be37c4a27ff5062 David Wilson <dw@botanicus.net> 1497289486 +0100 clone: from https://....:x-oauth-basic@github.com/dw/csvmonkey.git If you perform a Git checkout on a web server e.g. as part of an Ansible script, and you embedded secrets in the repo URL (common enough, believe me)
Read the rest
, then that secret is readable per above. FWIW this isn't some unbelievable theory or hypothetical scenario, I've seen plenty of Ansible setups like this and found domains with this exact problem in the process of writing http://pythonsweetness.tumblr.com/post/52587443706/devs-plea... a few years back
In Don't publicly expose .git (2015)

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.