supply-chain-attack-recon

To detect dependency-confusion risks, this Skill collects OSINT from public GitHub organizations and registries to identify internal-looking package names and assess registry exposures. It analyzes SBOM data and CI/CD configurations to surface actionable findings with severity and remediation guidance.

Supply-chain attack surface mapping identifies and exposes external risks like dependency-confusion, typosquats, and vulnerable workflows in software ecosystems. It collects OSINT from GitHub, public registries, and SBOM data to analyze exposure patterns before exploitation occurs.

Yes, you can use OSINT to find typosquat candidates by running the external-recon workflow against targets with public registries. The Skill analyzes public package names and registry exposures to surface potential typosquat targets for defensive hardening.

To check CI/CD workflows for vulnerable injection patterns, the Skill analyzes public GitHub workflow configurations and artifacts. It detects insecure CI/CD configurations and vulnerable workflow patterns that enable supply-chain abuse, then outputs actionable findings with remediation guidance.

The best way to assess SBOM leakage is using OSINT-driven discovery to collect and analyze SBOM data from public repositories. This Skill surfaces dependency-confusion targets and SBOM leakage during external assessments to prioritize defensive monitoring.

Yes, you need targets with public GitHub organizations, public registries, or SBOMs to map external supply-chain risks. The Skill relies on collecting OSINT from these public sources to identify dependency-confusion, typosquat, and workflow-injection exposures.