HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dweinstein
canary
Go2026–2026
dweinstein / canary

canary

Tiny filesystem honeypot for macOS. Mounts fake secret files (.env, id_rsa, credentials.json) via WebDAV (no root) or NFS (root) — any access triggers an alert. Zero dependencies, pure Go stdlib.

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

What to know before exploring

What it is

Tiny filesystem honeypot for macOS. Mounts fake secret files (.env, id_rsa, credentials.json) via WebDAV (no root) or NFS (root) — any access triggers an alert. Zero dependencies, pure Go stdlib.

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 day4 dated mentions

Observed mentions: 2026-03-24 21:18:11 UTC to 2026-04-14 03:33:48 UTC.

012026-03-24 00:00:00 UTC to 2026-03-25 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 242026-03-25 00:00:00 UTC to 2026-03-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-26 00:00:00 UTC to 2026-03-27 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-03-27 00:00:00 UTC to 2026-03-28 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-03-28 00:00:00 UTC to 2026-03-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-29 00:00:00 UTC to 2026-03-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-30 00:00:00 UTC to 2026-03-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-31 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-01 00:00:00 UTC to 2026-04-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-02 00:00:00 UTC to 2026-04-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-03 00:00:00 UTC to 2026-04-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 32026-04-04 00:00:00 UTC to 2026-04-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-05 00:00:00 UTC to 2026-04-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-06 00:00:00 UTC to 2026-04-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-07 00:00:00 UTC to 2026-04-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-08 00:00:00 UTC to 2026-04-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-09 00:00:00 UTC to 2026-04-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-10 00:00:00 UTC to 2026-04-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-11 00:00:00 UTC to 2026-04-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-12 00:00:00 UTC to 2026-04-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-13 00:00:00 UTC to 2026-04-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-14 00:00:00 UTC to 2026-04-15 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsApr 14

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
Mar 242026-03-24 00:00:00 UTC2026-03-25 00:00:00 UTC101
Mar 252026-03-25 00:00:00 UTC2026-03-26 00:00:00 UTC000
Mar 262026-03-26 00:00:00 UTC2026-03-27 00:00:00 UTC101
Mar 272026-03-27 00:00:00 UTC2026-03-28 00:00:00 UTC110
Mar 282026-03-28 00:00:00 UTC2026-03-29 00:00:00 UTC000
Mar 292026-03-29 00:00:00 UTC2026-03-30 00:00:00 UTC000
Mar 302026-03-30 00:00:00 UTC2026-03-31 00:00:00 UTC000
Mar 312026-03-31 00:00:00 UTC2026-04-01 00:00:00 UTC000
Apr 12026-04-01 00:00:00 UTC2026-04-02 00:00:00 UTC000
Apr 22026-04-02 00:00:00 UTC2026-04-03 00:00:00 UTC000
Apr 32026-04-03 00:00:00 UTC2026-04-04 00:00:00 UTC000
Apr 42026-04-04 00:00:00 UTC2026-04-05 00:00:00 UTC000
Apr 52026-04-05 00:00:00 UTC2026-04-06 00:00:00 UTC000
Apr 62026-04-06 00:00:00 UTC2026-04-07 00:00:00 UTC000
Apr 72026-04-07 00:00:00 UTC2026-04-08 00:00:00 UTC000
Apr 82026-04-08 00:00:00 UTC2026-04-09 00:00:00 UTC000
Apr 92026-04-09 00:00:00 UTC2026-04-10 00:00:00 UTC000
Apr 102026-04-10 00:00:00 UTC2026-04-11 00:00:00 UTC000
Apr 112026-04-11 00:00:00 UTC2026-04-12 00:00:00 UTC000
Apr 122026-04-12 00:00:00 UTC2026-04-13 00:00:00 UTC000
Apr 132026-04-13 00:00:00 UTC2026-04-14 00:00:00 UTC000
Apr 142026-04-14 00:00:00 UTC2026-04-15 00:00:00 UTC110

What Hacker News says

4 sources

Show HN: Tiny filesystem honeypot for macOS with zero dependencies in Go

When malware, a rogue script, npm module, or an attacker with shell access starts scanning your home directory for credentials, the canary trips and fires an alert. Developer's computers are increasingly being targeted with attacks, for example the LiteLLM attacks demonstrate the recent risks and complex supply chain attacks. I made this tool for macOS systems that helps detect when a package accesses something it shouldn't. It's a tiny go binary (less than 2k LOC) with no dependencies that will mount a webdav filesystem (no root) or NFS (root required) with fake secrets and send you a notification when anything accesses it. Very stupid simple. I've always really liked the canary/honeypot approach and this at least may give some folks a chance to detect (similar to like LittleSnitch) when something strange is going on! When to use which m
Read the rest
ode? Use WebDAV for low-friction canaries you can spin up anywhere. Use NFS for canaries that need to survive an attacker who has your user shell and is looking around.
2 points · Open discussion
https://github.com/dweinstein/canary I made this tool for macos systems that helps detect when a package accesses something it shouldn't. it's a tiny go binary (less than 2k LOC) with no dependencies that will mount a webdav filesystem (no root) or NFS (root required) with fake secrets and send you a notification when anything accesses it. Very stupid simple. I've always really liked the canary/honeypot approach and this at least may give some folks a chance to detect (similar to like LittleSnitch) when something strange is going on! Next time the attack may not have an obvious performance issue!
In Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised

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.