techstack-osint

Identify technology stacks from public repositories, career pages, and Wayback Machine snapshots.

3|1|Updated May 26, 2026
One-click install
npx skills add https://github.com/LeoWSY-hashblue/-communitytools-custom --skill techstack-osint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: techstack-osint
Source: https://github.com/LeoWSY-hashblue/-communitytools-custom/tree/main/skills/techstack-identification/osint
Command: npx skills add https://github.com/LeoWSY-hashblue/-communitytools-custom --skill techstack-osint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OSINT-based tech-stack identification from public sources helps analysts map a target's technology stack without direct access, reducing guesswork and enabling evidence-based decisions.

Core Features & Use Cases

  • Public repos: org metadata, language map, dependency files, CI configs, Dockerfile FROM lines
  • Career signals: career pages, ATS platforms, and job-description text
  • Web archives: Wayback Machine CDX queries to detect historical stack and migrations
  • Inference: languages, frameworks, base images, cloud usage, and migration history

Quick Start

Instruct the tool to scan public repos, ATS pages, and Wayback snapshots to surface the tech stack signals for a given domain.

Frequently Asked Questions about techstack-osint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify a company's tech stack from public OSINT sources?

To identify a tech stack from public OSINT sources, you analyze public code repositories, career pages, and Wayback Machine snapshots. This infers languages, frameworks, dependencies, and cloud usage from dependency files, CI configs, and archived metadata.

How do I detect historical tech stack migrations using the Wayback Machine?

Detect historical tech stack migrations using the Wayback Machine by querying CDX APIs for archived snapshots. Parsing this archive metadata reveals past dependencies and frameworks, enabling you to reconstruct a coherent timeline of stack changes.

Can I infer cloud usage and frameworks from public code repositories?

Yes, you can infer cloud usage and frameworks from public code repositories. Parsing dependency files, CI configs, and Dockerfile FROM lines extracts base images and infrastructure signals to map the active technology stack.

What OSINT data is needed to map a technology stack?

Mapping a technology stack requires public-facing OSINT data like org metadata, language maps, dependency files, CI configs, and career page text. Parsing these sources produces a coherent tech-stack timeline with confidence levels.

How do career pages and ATS signals help determine a tech stack?

Career pages and ATS signals help determine a tech stack by exposing job-description text and platform data. Analyzing these career signals reveals requested languages, frameworks, and dependencies, confirming the target's current technology stack.

Does this OSINT tech stack identification approach work without direct system access?

Yes, OSINT tech stack identification works without direct system access. It maps a target's technology stack by parsing public signals from repos, career pages, and web archives, reducing guesswork and enabling evidence-based decisions.