17 August 2026

The briefing as it was published on this date. Every entry was seen moving by at least two unrelated collectors that day. Where a follow-up exists, it shows what has happened since.

Entries: 2
With follow-up: 1

← Latest briefing Newer: 19 August 2026 Older: 16 August 2026

01/

Briefing · 17 August 2026

2 entries

01New

jitpass.com

Website · seen by Search volume, GitHub, HackerNews, Pricing page, Wikipedia

jit, a macOS command line tool that finds the credentials sitting in plain text on a developer's machine, in .env files, ~/.aws/credentials, shell exports, .npmrc tokens and MCP configs, and moves them behind Touch ID. Each secret is then handed to the process that asks for it only at the moment it runs. Free, local only, written in Go.

Why it is here

Stars went 93 to 115, up 23.7%, behind a HackerNews thread that went 69 comments to 78 while its points moved only 49 to 51. More comments than points is an argument rather than a wave, which for a tool that puts itself between every credential on a developer machine and the tools that read them is the reaction to expect. A month old, and two unrelated collectors saw it move on the same day.

02New

djc/oxish

Repository · seen by GitHub, HackerNews, Lobsters

OxiSH, an SSH server written from scratch in Rust rather than a binding around an existing one. Where it sits is the point: sshd is the daemon most machines leave exposed to the open internet, it has to handle authentication before it can trust anything, and the implementations in wide use are written in C. Dual licensed MIT and Apache 2.0.

Flagged 8 days ago · 253 → 335 stars · +32.4%

Why it is here

Stars 113 to 253, up 123.9%, and forks 5 to 10, measured across three days, 14 to 17 August. Open issues 5 to 10 and Lobsters points 7 to 53: people running it, not bookmarking it.

02/

Get it by email

Every morning

The briefing is written once a day. Leave an address and it comes to you instead of you coming to it.

One email a day. Unsubscribe in one click.

03/

Other briefings

26 archived

04/

How to read this

Method

Every number here is a rate of change, never a total. Size is not news. The largest repository on GitHub is not rising, it arrived years ago. What this looks for is movement, and specifically movement that more than one unrelated source noticed on the same day.

That second condition is the whole method. Stars can be bought, backlinks can be built, app installs can be farmed. This project has already killed 2,601 domains for sitting inside link networks, one of which ran to 2,046 sites and covered 98% of everything it tracked on .it. All of them were manufacturing the exact signal one of these sources measures. Faking two unrelated signals at once is far harder work, so a repository seen moving by GitHub and HackerNews, or an app seen by the App Store and Google Play, counts for more than a bigger number in one place.

Whether two sources are genuinely independent is measured rather than assumed. Majestic ranks domains by backlinks and Tranco ranks them by traffic, and the two were treated as one voice for weeks. Comparing their daily movement across 83,000 domains showed no relationship at all, so they now count as two. Any pair that turns out to share data underneath gets folded back into one.

Entries are written to be read rather than scanned. When the evidence is thin, or the story behind it does not hold up, the entry is left out rather than published with a caveat.