signalproof-supply-chain

Review dependency provenance, licenses, integrity evidence, and rollback paths before trusting external components.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-supply-chain-docreo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signalproof-supply-chain
Source: https://github.com/docreo/Signalproof-Skills/tree/main/skills/signalproof-supply-chain
Command: npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-supply-chain-docreo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams routinely install third-party dependencies without verifying their source, license, integrity, or removal path, creating hidden security, legal, and operational risk. This Skill turns every dependency decision into an evidence-backed review instead of a blind installation step. ## Core Features & Use Cases - Provenance and Identity Verification: Confirm canonical source, publisher, exact version, and immutable identity before trusting a component. - License and Integrity Review: Record license and redistribution implications, prefer pinned versions with verified hashes or signatures, and inspect install/update hooks proportionately to risk. - Risk Dispositions and STOP Conditions: Classify components with explicit dispositions (e.g., INTEGRATION CANDIDATE, LICENSE / PROVENANCE BLOCKED, REJECT / STOP) and halt when provenance is missing or rollback is unavailable. - Use Case: Before adding a new npm package to a production service, use this Skill to verify the publisher, pin the version with a checksum, check known advisories, document transitive dependencies, and define a removal path. ## Quick Start Ask the AI to review a specific dependency using the signalproof-supply-chain contract before integrating it into your project.

Frequently Asked Questions about signalproof-supply-chain

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

FAQPage Schema
How do I review a dependency before adding it to my project?▼

Verify the canonical source and publisher, pin an exact version with a verified hash or signature, record the license, inspect install and update scripts, and define a rollback path. This Skill structures that review into explicit contract steps and dispositions.

What should I check in a package's supply chain security?▼

Check source and publisher identity, immutable version references, checksums or signatures, install/build hooks, network and update behavior, required permissions, transitive dependencies, and known advisories material to your decision.

When should a dependency review stop instead of proceeding?▼

Stop when the source cannot be established, license obligations conflict with intended use, an executable install path lacks adequate trust basis, a mutable artifact is presented as frozen, or no removal path exists for a consequential integration.

Does this Skill decide whether to adopt a dependency?▼

No. It produces evidence-backed dispositions such as INTEGRATION CANDIDATE or LICENSE / PROVENANCE BLOCKED, but strategic ADOPT, ADAPT, or REJECT decisions remain with the Evaluate function and the human owner.

Why is pinning versions preferred over using latest tags?▼

Mutable references like latest can change silently, breaking integrity guarantees and reproducibility. Pinned versions with verified hashes or signatures ensure the reviewed artifact is exactly what gets installed.