Menu

The open source references I keep in my own account (standalone editions, honestly labelled)
📰

The open source references I keep in my own account (standalone editions, honestly labelled)

DEV Community: github·Syed Mujtaba·6 days ago
#LNtt9Wxa
#devtogithub#technology#devto#dev#standalone
Reading 0:00
15s threshold

Quick honesty note before anything else: none of the projects below are mine. They are well known open source references that I keep as standalone editions in my GitHub account, each one credited to its upstream project in the repo description and README, because I actually use them in my daily work as a full-stack developer.

Why keep your own editions at all? Three reasons. My tooling keeps working even if an upstream repo moves. I can pin the exact version my workflow depends on. And I add a small enhancement layer on top: standardised docs, dependabot, CI and lint, so every edition behaves the same way in my setup.

The ones that earn their keep:

public-apis, standalone edition ( https://github.com/mujtbabbas/public-apis )

The collective list of free APIs. Original: public-apis/public-apis. I reach for it at the start of almost every integration.

free-for-dev, standalone edition ( https://github.com/mujtbabbas/free-for-dev )

Free tiers of SaaS, PaaS and IaaS offerings.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.