scan-package

Scan Python and Node.js packages with Sigil before installation.

5|2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/NOMARJ/sigil --skill scan-package
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scan-package
Source: https://github.com/NOMARJ/sigil/tree/main/plugins/claude-code/skills/scan-package
Command: npx skills add https://github.com/NOMARJ/sigil --skill scan-package

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify and block risky Python (pip) and Node.js (npm) packages before installation, reducing supply chain risk and potential agent compromise.

Core Features & Use Cases

  • Pre-install package scanning for pip and npm using Sigil
  • Flags risky patterns like install hooks, network calls, or credential access
  • Use during dependency updates or new package installations to enforce safe behavior

Quick Start

Run Sigil to scan a package before installation and review the findings.

Frequently Asked Questions about scan-package

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

FAQPage Schema
How do I scan npm and pip packages for security risks before installation?

To scan npm and pip packages for security risks before installation, you can apply a pre-install scanning workflow using the Sigil CLI to automatically identify and block risky packages during dependency updates.

What risky patterns are flagged during a package pre-install scan?

A package pre-install scan flags risky patterns such as install hooks, unauthorized network calls, and credential access attempts to prevent supply chain attacks and potential agent compromise.

Do I need the Sigil CLI to run pre-install scans for Node.js and Python projects?

Yes, you need the Sigil CLI to run pre-install scans for Node.js and Python projects, as it executes the package analysis to enforce safe behavior before npm or pip installations proceed.

When should I use a pre-install package scan in my development workflow?

You should use a pre-install package scan during dependency updates, new package installations, or npm installs to ensure safe behavior and reduce supply chain risk before packages are added to your project.

Can I block risky Node.js packages before they are installed?

You can block risky Node.js packages before installation by enforcing a pre-install scan that identifies install hooks, network calls, and credential access patterns using the Sigil CLI.