The Problem

Investigators and analysts often waste time locating reliable OSINT utilities. The market lacks a single, curated, searchable inventory that spans social, aviation, maritime, cyber‑threat, and other niches, while also providing a lightweight way to keep links current.

What This Does

Legendary_OSINT aggregates 31 markdown files under docs/ (e.g., docs/people-social.md, docs/maritime.md, docs/ai-osint.md) that each list tools, APIs, and reference sites for a specific domain. The repository’s root files—README.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md, LICENSE—explain contribution rules and licensing (CC0 1.0). A single GitHub Actions workflow (.github/workflows/da-link-checkah.yml) runs the lychee link‑checker against all markdown files, using an ignore list in .lycheeignore.

How It Is Wired

  • Entry point – There is no executable code; the only active process is the CI workflow.
  • Workflow – On every push (and on a schedule), GitHub Actions triggers da-link-checkah.yml.
  • The job checks out the repo, installs lychee-action (lycheeverse/lychee-action@v2), and runs it against ./**/*.md.
  • Results are posted to the Actions UI; failures block the merge.
  • Supporting files –
  • .lycheeignore enumerates URL patterns that the checker should skip.
  • Each docs/*.md file is a static list; no scripts read or modify them.
  • Impact surface – The only side‑effects are the CI runner’s network calls to external URLs. No database, filesystem writes, or external services are invoked by the repository itself.

How To Use It

# Clone the collection
git clone https://github.com/moses-y/Legendary_OSINT.git
cd Legendary_OSINT

# Browse the curated lists locally
open docs/people-social.md   # macOS; use any markdown viewer

If you want to run the link check locally (outside GitHub Actions):

# Requires Docker
docker run --rm -v "$(pwd)":/workdir lycheeverse/lychee-action \
  -v -n -r -i .lycheeignore "./**/*.md"

No additional build steps, package managers, or environment variables are required.

Real‑World Use

A cyber‑threat intelligence team can script a nightly pull:

#!/usr/bin/env bash
git -C ~/osint pull
cp ~/osint/docs/malware-cti.md ~/internal/wiki/malware-tools.md

The copied markdown becomes part of the internal knowledge base, ensuring analysts always see the latest vetted toolset without maintaining their own list.

Code Health & Issues

  • High – Pin third‑party GitHub Action to a commit SHA (.github/workflows/da-link-checkah.yml uses lycheeverse/lychee-action@v2).
  • Medium – Declare least‑privilege permissions for GITHUB_TOKEN (workflow currently declares none).
  • Low – Set timeout-minutes on workflow jobs (none defined, defaults to 6 h).
  • Testing – No test files detected; code paths (the CI job) are untested.
  • CI – Present (GitHub Actions).
  • License – CC0 1.0 Universal included.
  • Secrets – No committed secrets found.

The Bottom Line

Legendary_OSINT delivers a well‑organized, freely reusable OSINT reference library, ideal for analysts who need a single source of truth. Its only runtime component is a link‑checking CI job, which currently lacks best‑practice hardening (pinned actions, scoped token permissions, job timeouts). Adding those fixes and any automated validation tests would raise the repo’s operational safety without altering its core value.