guarddog-security-scan

Audit Python and Node.js dependencies for malware before installation.

17|5|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/alxayo/sec-check --skill guarddog-security-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guarddog-security-scan
Source: https://github.com/alxayo/sec-check/tree/main/.github/skills/guarddog-security-scan
Command: npx skills add https://github.com/alxayo/sec-check --skill guarddog-security-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams verify third-party dependencies for malware and supply-chain risks before installation, preventing risky packages from being installed into their projects.

Core Features & Use Cases

  • Audit PyPI and npm dependencies prior to install by scanning requirements.txt, package.json, and package-lock.json for malicious patterns.
  • Detect typosquatting, obfuscated payloads, and compromised maintainers in dependencies.
  • Pre-install checks for risk indicators in local and remote packages to reduce supply-chain risk.

Quick Start

Ask GuardDog to scan a project’s dependencies before running pip install or npm install.

Frequently Asked Questions about guarddog-security-scan

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

FAQPage Schema
How do I scan Python and Node.js dependencies for malware before installation?

You can scan Python and Node.js dependencies for malware by auditing requirements.txt, package.json, and package-lock.json files to detect malicious patterns and supply-chain risks before running pip or npm install.

What types of supply-chain risks can be detected in npm and PyPI packages?

Supply-chain scans detect typosquatting, obfuscated payloads, and compromised maintainers in npm and PyPI packages by applying source-code rules and metadata heuristics to identify malicious indicators.

Can I check both local projects and remote packages for malicious patterns?

Yes, you can perform pre-install checks for risk indicators in both local project directories and remote packages to reduce supply-chain risk before adding dependencies.

How do I audit package-lock.json and requirements.txt for compromised maintainers?

Auditing package-lock.json and requirements.txt for compromised maintainers involves analyzing dependency metadata and source code using heuristic rules to flag suspicious package behaviors.

Does this dependency scan work with both Python and Node.js project archives?

Yes, the dependency scan works with both Python and Node.js project archives, targeting requirements.txt, package.json, package-lock.json, and related files to detect malicious patterns.

What is the best way to prevent installing malicious npm or PyPI packages?

The best way to prevent installing malicious npm or PyPI packages is to run pre-install dependency audits that scan for typosquatting and obfuscated payloads before executing pip install or npm install.