maxtac-supply-chain-oss-proof-gate

Automate OSS proof-gating and validate evidence for supply-chain findings.

12|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/philo-groves/MaxTAC --skill maxtac-supply-chain-oss-proof-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maxtac-supply-chain-oss-proof-gate
Source: https://github.com/philo-groves/MaxTAC/tree/main/plugins/maxtac-supply-chains/skills/maxtac-supply-chain-oss-proof-gate
Command: npx skills add https://github.com/philo-groves/MaxTAC --skill maxtac-supply-chain-oss-proof-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the proof-gating process for open-source supply-chain findings, ensuring they meet reportable standards before reporting.

Core Features & Use Cases

  • Automated Proof Gating: Automates the decision-making process for whether an OSS, dependency, or package finding should be reported.
  • Use Case: Before reporting an issue in a supply chain, this Skill helps decide if the evidence supports a reportable issue, needs more product impact proof, should be addressed by third-party owners, or if it is not actionable.

Quick Start

Use maxtac-supply-chain-oss-proof-gate create --output tmp/supply-chain/<case-id>/oss-proof-gate.md --case-id <case-id> --target "package or project" --ecosystem npm --claim "dependency confusion reaches release CI".

Frequently Asked Questions about maxtac-supply-chain-oss-proof-gate

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

FAQPage Schema
What is supply chain OSS proof gating for dependency findings?

Supply chain OSS proof gating validates evidence for scope, ownership, impact, and security to decide if dependency findings meet reportable standards before reporting. It ensures issues have sufficient product impact proof or should be addressed by third-party owners.

How do I automate proof gating for open-source security findings before reporting?

You can automate open-source security proof gating by running the create command with a target package, ecosystem, and claim. This generates a markdown packet that lints evidence and determines if the finding is actionable or needs more proof.

When do I need to validate dependency confusion evidence for a release CI pipeline?

You need to validate dependency confusion evidence when you have a security claim affecting release CI pipelines. The proof gate checks if the evidence aligns with real-world implications and OSS rules to determine if the finding is reportable.

Can I use this proof gate to check if a package vulnerability should be addressed by third-party owners?

Yes, the proof gate evaluates ownership and scope within the supply chain. It determines whether package vulnerability findings have enough impact proof to report internally or should be routed to third-party maintainers instead.

Does the automated supply chain proof gate require specific scripts to run?

Yes, the process requires the scripts/oss_gate.py script to create and lint evidence packets. This script automates the validation of scope, ownership, impact, and security issues for dependency findings.