concept · behind your stack · a feature idea for /dev/null

Your stack knows who to follow.

When you sign up, /dev/null reads the composer.json and package.json of your latest public repositories and suggests the people behind the packages you use. Type a GitHub username to see who that would be.

Or try @nunomaduro, @taylorotwell or @freekmurze.

10 latest repos
20 packages
top 5 contributors each
0 servers

Behind your stack who --should-i-follow

How it works

repos: The 10 most recently pushed public repositories you own, forks left out
manifests: composer.json and package.json at their root, the first 100 KB
packages: The 20 used by the most of those repositories, @types/* left out
people: The top 5 GitHub contributors to each package's repository, bots left out
suggested: Whoever of them is already on /dev/null, for your first week
requests: Straight from your browser to GitHub, Packagist, npm and /dev/null's public API
stored: Nothing on a server. This browser keeps a day of lookups so a second try is free

Suggested, not followed

On /dev/null, anyone you follow can message you in Remotes. So the people behind your stack are suggested, marked Behind your stack, and following stays your call.

Why

As /dev/null grows, Nuno wants newcomers connected right away to the people around the topics they care about.

Your dependencies already say which topics those are.