Check the source
HTTP responses, redirects and repository metadata are recorded with a timestamp. Corrected links retain the original result and a separate replacement check. Bot restrictions remain “access limited.”
THE LIVING FIELD GUIDE / VOL. 01
A better tool
for the right job.
Intelligence, visibility, privacy and security. A practical map of what exists, what it’s for, and what deserves a closer look.
Find your next tool- Resources
- 395
- API / services
- —
- Last audit
- —
THE UTILITY MAPChoose a field to explore
Loading dated availability checks…
EXPLORE THE COLLECTION
Useful starts here.
Every entry has a purpose.
Every status has a date.
What “configured” means. These providers were identified from private integration references in Infisical and Railway. Configuration does not prove a successful API call, a paid balance, or an enabled production workflow. The public view contains provider names and purposes; credential references remain private.
EVIDENCE, BEFORE ENTHUSIASM
An available link
is a starting point.
We keep source availability, maintenance activity, and functional testing separate. A live website can point to an old project; a recent commit is not a security audit.
Machine-readable collection ↗Agent reference ↗Download CSV ↗State the limits
Repository activity is a maintenance signal. “Not tested” stays visible until a scoped evaluation establishes actual behavior.
Choose by purpose
Priorities are an evaluation order for our work, not endorsements. Project ideas and learning references stay distinct from ready-to-use software.
Keep it current
Daily source watching and weekly availability checks feed this collection. New entries and meaningful changes are reviewed before publication.