[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DARDM9P6VPN8QXNPDDZGEF":3,"skill-same:01M7DARDM9P6VPN8QXNPDDZGEF":106},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M7DARDM9P6VPN8QXNPDDZGEF","implementing-supply-chain-security-with-in-toto",null,"Implement software supply chain integrity verification for container builds using the in-toto framework, covering signing-key generation, defining a supply chain layout, recording pipeline steps as signed link metadata, verifying before deployment, Kubernetes admission control, and SLSA integration. Use when generating in-toto attestations for CI\u002FCD pipeline steps, verifying that a container image followed an approved build process, or enforcing supply chain provenance at admission time.","SaiVatsal\u002FSkills-I-Use","SaiVatsal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F242597752?v=4","01M7D5YM1T4VXW9203M0GFAHZ1","SaiVatsalPolimera","01M7D5YM2D61ST39XVR2V7B7ZJ",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-supply-chain-security-with-in-toto\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-supply-chain-security-with-in-toto\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-supply-chain-security-with-in-toto\ndescription: Implement software supply chain integrity verification for container\n  builds using the in-toto framework, covering signing-key generation, defining a\n  supply chain layout, recording pipeline steps as signed link metadata, verifying\n  before deployment, Kubernetes admission control, and SLSA integration. Use when\n  generating in-toto attestations for CI\u002FCD pipeline steps, verifying that a container\n  image followed an approved build process, or enforcing supply chain provenance\n  at admission time.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- in-toto\n- supply-chain-security\n- attestation\n- slsa\n- sigstore\n- container-security\n- cncf\n- provenance\n- sbom\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.IR-01\n- ID.AM-08\n- DE.CM-01\nmitre_attack:\n- T1610\n- T1611\n- T1609\n- T1525\n- T1195\n---\n\n# Implementing Supply Chain Security with in-toto\n\n## Overview\n\nin-toto is a CNCF graduated project that ensures the integrity of software supply chains from initiation to end-user installation. It creates a verifiable record of the entire software development lifecycle by generating cryptographically signed attestations (called \"link metadata\") at each step, proving what happened, who performed it, and what artifacts were produced. For container environments, in-toto verifies that images deployed to Kubernetes followed approved build processes and have not been tampered with.\n\n\n## When to Use\n\n- When deploying or configuring implementing supply chain security with in toto capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Python 3.8+ or Go runtime for in-toto client libraries\n- GPG or Ed25519 keys for signing attestations\n- Container build pipeline (Docker, Buildah, or Kaniko)\n- Container registry (Docker Hub, ECR, GCR, or Harbor)\n- Kubernetes cluster for deployment verification\n\n## Core Concepts\n\n### Supply Chain Layout\n\nThe layout is the central policy document that defines:\n\n- **Steps**: Ordered operations in the supply chain (clone, build, test, package, push)\n- **Functionaries**: Authorized entities (people or CI systems) that perform each step\n- **Inspections**: Client-side verification checks performed at verification time\n- **Expected artifacts**: Input\u002Foutput relationships between steps\n\n```python\nfrom in_toto.models.layout import Layout, Step, Inspection\nfrom securesystemslib.interface import import_ed25519_privatekey_from_file\n\n# Create the supply chain layout\nlayout = Layout()\nlayout.set_relative_expiration(months=3)\n\n# Define the code clone step\nstep_clone = Step(name=\"clone\")\nstep_clone.expected_materials = []\nstep_clone.expected_products = [[\"CREATE\", \"src\u002F*\"]]\nstep_clone.pubkeys = [clone_functionary_keyid]\nstep_clone.expected_command = [\"git\", \"clone\"]\nstep_clone.threshold = 1\n\n# Define the build step\nstep_build = Step(name=\"build\")\nstep_build.expected_materials = [[\"MATCH\", \"src\u002F*\", \"WITH\", \"PRODUCTS\", \"FROM\", \"clone\"]]\nstep_build.expected_products = [[\"CREATE\", \"image.tar\"]]\nstep_build.pubkeys = [build_functionary_keyid]\nstep_build.expected_command = [\"docker\", \"build\"]\nstep_build.threshold = 1\n\n# Define the scan step\nstep_scan = Step(name=\"scan\")\nstep_scan.expected_materials = [[\"MATCH\", \"image.tar\", \"WITH\", \"PRODUCTS\", \"FROM\", \"build\"]]\nstep_scan.expected_products = [[\"CREATE\", \"scan-report.json\"]]\nstep_scan.pubkeys = [scan_functionary_keyid]\nstep_scan.threshold = 1\n\nlayout.steps = [step_clone, step_build, step_scan]\n```\n\n### Link Metadata\n\nEach step execution generates a link file containing:\n\n- Materials consumed (input artifacts with hashes)\n- Products created (output artifacts with hashes)\n- Command executed\n- Cryptographic signature of the functionary\n\n### Verification Process\n\nAt deployment time, the verifier checks:\n1. All required steps were performed\n2. Each step was signed by an authorized functionary\n3. Artifact hashes chain correctly between steps\n4. No unauthorized modifications occurred between steps\n\n## Implementation\n\n### Step 1: Generate Signing Keys\n\n```bash\n# Generate Ed25519 key pairs for each functionary\nmkdir -p keys\n\n# Project owner key (signs the layout)\nin-toto-keygen --type ed25519 keys\u002Fowner\n\n# CI builder key\nin-toto-keygen --type ed25519 keys\u002Fbuilder\n\n# Security scanner key\nin-toto-keygen --type ed25519 keys\u002Fscanner\n```\n\n### Step 2: Create the Supply Chain Layout\n\n```python\n#!\u002Fusr\u002Fbin\u002Fenv python3\n\"\"\"Generate in-toto supply chain layout for container builds.\"\"\"\n\nfrom in_toto.models.layout import Layout, Step, Inspection\nfrom in_toto.models.metadata import Envelope\nfrom securesystemslib.signer import CryptoSigner\nfrom securesystemslib.interface import import_ed25519_publickey_from_file\n\ndef create_container_build_layout():\n    layout = Layout()\n    layout.set_relative_expiration(months=6)\n\n    # Load functionary public keys\n    builder_key = import_ed25519_publickey_from_file(\"keys\u002Fbuilder.pub\")\n    scanner_key = import_ed25519_publickey_from_file(\"keys\u002Fscanner.pub\")\n\n    layout.keys = {\n        builder_key[\"keyid\"]: builder_key,\n        scanner_key[\"keyid\"]: scanner_key,\n    }\n\n    # Step 1: Source code checkout\n    checkout = Step(name=\"checkout\")\n    checkout.expected_materials = []\n    checkout.expected_products = [\n        [\"CREATE\", \"Dockerfile\"],\n        [\"CREATE\", \"src\u002F*\"],\n        [\"CREATE\", \"requirements.txt\"],\n    ]\n    checkout.pubkeys = [builder_key[\"keyid\"]]\n    checkout.threshold = 1\n\n    # Step 2: Build container image\n    build = Step(name=\"build\")\n    build.expected_materials = [\n        [\"MATCH\", \"Dockerfile\", \"WITH\", \"PRODUCTS\", \"FROM\", \"checkout\"],\n        [\"MATCH\", \"src\u002F*\", \"WITH\", \"PRODUCTS\", \"FROM\", \"checkout\"],\n    ]\n    build.expected_products = [[\"CREATE\", \"image-digest.txt\"]]\n    build.pubkeys = [builder_key[\"keyid\"]]\n    build.threshold = 1\n\n    # Step 3: Security scan\n    scan = Step(name=\"scan\")\n    scan.expected_materials = [\n        [\"MATCH\", \"image-digest.txt\", \"WITH\", \"PRODUCTS\", \"FROM\", \"build\"]\n    ]\n    scan.expected_products = [\n        [\"CREATE\", \"vulnerability-report.json\"],\n        [\"CREATE\", \"sbom.json\"],\n    ]\n    scan.pubkeys = [scanner_key[\"keyid\"]]\n    scan.threshold = 1\n\n    # Inspection: Verify no critical vulnerabilities\n    inspect_vulns = Inspection(name=\"verify-no-critical-vulns\")\n    inspect_vulns.expected_materials = [\n        [\"MATCH\", \"vulnerability-report.json\", \"WITH\", \"PRODUCTS\", \"FROM\", \"scan\"]\n    ]\n    inspect_vulns.run = [\n        \"python\", \"-c\",\n        \"import json,sys; r=json.load(open('vulnerability-report.json')); \"\n        \"sys.exit(1) if any(v['severity']=='CRITICAL' for v in r.get('vulnerabilities',[])) else sys.exit(0)\"\n    ]\n\n    layout.steps = [checkout, build, scan]\n    layout.inspect = [inspect_vulns]\n\n    return layout\n\nif __name__ == \"__main__\":\n    layout = create_container_build_layout()\n    # Sign with owner key and save\n    owner_signer = CryptoSigner.from_priv_key_uri(\"file:keys\u002Fowner\")\n    envelope = Envelope.from_signable(layout)\n    envelope.create_signature(owner_signer)\n    envelope.dump(\"root.layout\")\n    print(\"Layout created and signed: root.layout\")\n```\n\n### Step 3: Record Pipeline Steps\n\n```bash\n# In CI\u002FCD pipeline - record each step\n\n# Step 1: Checkout\nin-toto-run --step-name checkout \\\n  --key keys\u002Fbuilder \\\n  --products Dockerfile src\u002F* requirements.txt \\\n  -- git clone https:\u002F\u002Fgithub.com\u002Forg\u002Fapp.git .\n\n# Step 2: Build\nin-toto-run --step-name build \\\n  --key keys\u002Fbuilder \\\n  --materials Dockerfile src\u002F* \\\n  --products image-digest.txt \\\n  -- bash -c \"docker build -t app:latest . && docker inspect --format='{{.Id}}' app:latest > image-digest.txt\"\n\n# Step 3: Scan\nin-toto-run --step-name scan \\\n  --key keys\u002Fscanner \\\n  --materials image-digest.txt \\\n  --products vulnerability-report.json sbom.json \\\n  -- bash -c \"trivy image --format json app:latest > vulnerability-report.json && syft app:latest -o json > sbom.json\"\n```\n\n### Step 4: Verify Before Deployment\n\n```bash\n# Verify the entire supply chain\nin-toto-verify --layout root.layout \\\n  --layout-key keys\u002Fowner.pub \\\n  --link-dir .\u002Flink-metadata\u002F\n\n# If verification passes, proceed with deployment\nif [ $? -eq 0 ]; then\n  kubectl apply -f deployment.yaml\n  echo \"Supply chain verification passed - deploying\"\nelse\n  echo \"SUPPLY CHAIN VERIFICATION FAILED - blocking deployment\"\n  exit 1\nfi\n```\n\n### Step 5: Kubernetes Admission Control\n\nIntegrate with a policy engine to verify attestations at admission:\n\n```yaml\napiVersion: admissionregistration.k8s.io\u002Fv1\nkind: ValidatingWebhookConfiguration\nmetadata:\n  name: in-toto-verifier\nwebhooks:\n  - name: verify.in-toto.io\n    rules:\n      - apiGroups: [\"apps\"]\n        resources: [\"deployments\"]\n        operations: [\"CREATE\", \"UPDATE\"]\n    clientConfig:\n      service:\n        name: in-toto-webhook\n        namespace: security\n        path: \u002Fverify\n    failurePolicy: Fail\n    sideEffects: None\n    admissionReviewVersions: [\"v1\"]\n```\n\n## SLSA Integration\n\nin-toto attestations map directly to SLSA (Supply chain Levels for Software Artifacts) requirements:\n\n| SLSA Level | in-toto Requirement |\n|------------|-------------------|\n| Level 1 | Build process documented (layout exists) |\n| Level 2 | Signed attestations from hosted build service |\n| Level 3 | Hardened build platform, non-falsifiable provenance |\n| Level 4 | Two-party review, hermetic builds |\n\n## References\n\n- [in-toto Official Website](https:\u002F\u002Fin-toto.io\u002F)\n- [in-toto GitHub Repository](https:\u002F\u002Fgithub.com\u002Fin-toto\u002Fin-toto)\n- [CNCF in-toto Graduation Announcement](https:\u002F\u002Fwww.cncf.io\u002Fannouncements\u002F2025\u002F04\u002F23\u002Fcncf-announces-graduation-of-in-toto-security-framework-enhancing-software-supply-chain-integrity-across-industries\u002F)\n- [SLSA Framework](https:\u002F\u002Fslsa.dev\u002F)\n- [Sigstore Integration](https:\u002F\u002Fwww.sigstore.dev\u002F)\n","# Implementing Supply Chain Security with in-toto\n\n## Overview\n\nin-toto is a CNCF graduated project that ensures the integrity of software supply chains from initiation to end-user installation. It creates a verifiable record of the entire software development lifecycle by generating cryptographically signed attestations (called \"link metadata\") at each step, proving what happened, who performed it, and what artifacts were produced. For container environments, in-toto verifies that images deployed to Kubernetes followed approved build processes and have not been tampered with.\n\n\n## When to Use\n\n- When deploying or configuring implementing supply chain security with in toto capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Python 3.8+ or Go runtime for in-toto client libraries\n- GPG or Ed25519 keys for signing attestations\n- Container build pipeline (Docker, Buildah, or Kaniko)\n- Container registry (Docker Hub, ECR, GCR, or Harbor)\n- Kubernetes cluster for deployment verification\n\n## Core Concepts\n\n### Supply Chain Layout\n\nThe layout is the central policy document that defines:\n\n- **Steps**: Ordered operations in the supply chain (clone, build, test, package, push)\n- **Functionaries**: Authorized entities (people or CI systems) that perform each step\n- **Inspections**: Client-side verification checks performed at verification time\n- **Expected artifacts**: Input\u002Foutput relationships between steps\n\n```python\nfrom in_toto.models.layout import Layout, Step, Inspection\nfrom securesystemslib.interface import import_ed25519_privatekey_from_file\n\n# Create the supply chain layout\nlayout = Layout()\nlayout.set_relative_expiration(months=3)\n\n# Define the code clone step\nstep_clone = Step(name=\"clone\")\nstep_clone.expected_materials = []\nstep_clone.expected_products = [[\"CREATE\", \"src\u002F*\"]]\nstep_clone.pubkeys = [clone_functionary_keyid]\nstep_clone.expected_command = [\"git\", \"clone\"]\nstep_clone.threshold = 1\n\n# Define the build step\nstep_build = Step(name=\"build\")\nstep_build.expected_materials = [[\"MATCH\", \"src\u002F*\", \"WITH\", \"PRODUCTS\", \"FROM\", \"clone\"]]\nstep_build.expected_products = [[\"CREATE\", \"image.tar\"]]\nstep_build.pubkeys = [build_functionary_keyid]\nstep_build.expected_command = [\"docker\", \"build\"]\nstep_build.threshold = 1\n\n# Define the scan step\nstep_scan = Step(name=\"scan\")\nstep_scan.expected_materials = [[\"MATCH\", \"image.tar\", \"WITH\", \"PRODUCTS\", \"FROM\", \"build\"]]\nstep_scan.expected_products = [[\"CREATE\", \"scan-report.json\"]]\nstep_scan.pubkeys = [scan_functionary_keyid]\nstep_scan.threshold = 1\n\nlayout.steps = [step_clone, step_build, step_scan]\n```\n\n### Link Metadata\n\nEach step execution generates a link file containing:\n\n- Materials consumed (input artifacts with hashes)\n- Products created (output artifacts with hashes)\n- Command executed\n- Cryptographic signature of the functionary\n\n### Verification Process\n\nAt deployment time, the verifier checks:\n1. All required steps were performed\n2. Each step was signed by an authorized functionary\n3. Artifact hashes chain correctly between steps\n4. No unauthorized modifications occurred between steps\n\n## Implementation\n\n### Step 1: Generate Signing Keys\n\n```bash\n# Generate Ed25519 key pairs for each functionary\nmkdir -p keys\n\n# Project owner key (signs the layout)\nin-toto-keygen --type ed25519 keys\u002Fowner\n\n# CI builder key\nin-toto-keygen --type ed25519 keys\u002Fbuilder\n\n# Security scanner key\nin-toto-keygen --type ed25519 keys\u002Fscanner\n```\n\n### Step 2: Create the Supply Chain Layout\n\n```python\n#!\u002Fusr\u002Fbin\u002Fenv python3\n\"\"\"Generate in-toto supply chain layout for container builds.\"\"\"\n\nfrom in_toto.models.layout import Layout, Step, Inspection\nfrom in_toto.models.metadata import Envelope\nfrom securesystemslib.signer import CryptoSigner\nfrom securesystemslib.interface import import_ed25519_publickey_from_file\n\ndef create_container_build_layout():\n    layout = Layout()\n    layout.set_relative_expiration(months=6)\n\n    # Load functionary public keys\n    builder_key = import_ed25519_publickey_from_file(\"keys\u002Fbuilder.pub\")\n    scanner_key = import_ed25519_publickey_from_file(\"keys\u002Fscanner.pub\")\n\n    layout.keys = {\n        builder_key[\"keyid\"]: builder_key,\n        scanner_key[\"keyid\"]: scanner_key,\n    }\n\n    # Step 1: Source code checkout\n    checkout = Step(name=\"checkout\")\n    checkout.expected_materials = []\n    checkout.expected_products = [\n        [\"CREATE\", \"Dockerfile\"],\n        [\"CREATE\", \"src\u002F*\"],\n        [\"CREATE\", \"requirements.txt\"],\n    ]\n    checkout.pubkeys = [builder_key[\"keyid\"]]\n    checkout.threshold = 1\n\n    # Step 2: Build container image\n    build = Step(name=\"build\")\n    build.expected_materials = [\n        [\"MATCH\", \"Dockerfile\", \"WITH\", \"PRODUCTS\", \"FROM\", \"checkout\"],\n        [\"MATCH\", \"src\u002F*\", \"WITH\", \"PRODUCTS\", \"FROM\", \"checkout\"],\n    ]\n    build.expected_products = [[\"CREATE\", \"image-digest.txt\"]]\n    build.pubkeys = [builder_key[\"keyid\"]]\n    build.threshold = 1\n\n    # Step 3: Security scan\n    scan = Step(name=\"scan\")\n    scan.expected_materials = [\n        [\"MATCH\", \"image-digest.txt\", \"WITH\", \"PRODUCTS\", \"FROM\", \"build\"]\n    ]\n    scan.expected_products = [\n        [\"CREATE\", \"vulnerability-report.json\"],\n        [\"CREATE\", \"sbom.json\"],\n    ]\n    scan.pubkeys = [scanner_key[\"keyid\"]]\n    scan.threshold = 1\n\n    # Inspection: Verify no critical vulnerabilities\n    inspect_vulns = Inspection(name=\"verify-no-critical-vulns\")\n    inspect_vulns.expected_materials = [\n        [\"MATCH\", \"vulnerability-report.json\", \"WITH\", \"PRODUCTS\", \"FROM\", \"scan\"]\n    ]\n    inspect_vulns.run = [\n        \"python\", \"-c\",\n        \"import json,sys; r=json.load(open('vulnerability-report.json')); \"\n        \"sys.exit(1) if any(v['severity']=='CRITICAL' for v in r.get('vulnerabilities',[])) else sys.exit(0)\"\n    ]\n\n    layout.steps = [checkout, build, scan]\n    layout.inspect = [inspect_vulns]\n\n    return layout\n\nif __name__ == \"__main__\":\n    layout = create_container_build_layout()\n    # Sign with owner key and save\n    owner_signer = CryptoSigner.from_priv_key_uri(\"file:keys\u002Fowner\")\n    envelope = Envelope.from_signable(layout)\n    envelope.create_signature(owner_signer)\n    envelope.dump(\"root.layout\")\n    print(\"Layout created and signed: root.layout\")\n```\n\n### Step 3: Record Pipeline Steps\n\n```bash\n# In CI\u002FCD pipeline - record each step\n\n# Step 1: Checkout\nin-toto-run --step-name checkout \\\n  --key keys\u002Fbuilder \\\n  --products Dockerfile src\u002F* requirements.txt \\\n  -- git clone https:\u002F\u002Fgithub.com\u002Forg\u002Fapp.git .\n\n# Step 2: Build\nin-toto-run --step-name build \\\n  --key keys\u002Fbuilder \\\n  --materials Dockerfile src\u002F* \\\n  --products image-digest.txt \\\n  -- bash -c \"docker build -t app:latest . && docker inspect --format='{{.Id}}' app:latest > image-digest.txt\"\n\n# Step 3: Scan\nin-toto-run --step-name scan \\\n  --key keys\u002Fscanner \\\n  --materials image-digest.txt \\\n  --products vulnerability-report.json sbom.json \\\n  -- bash -c \"trivy image --format json app:latest > vulnerability-report.json && syft app:latest -o json > sbom.json\"\n```\n\n### Step 4: Verify Before Deployment\n\n```bash\n# Verify the entire supply chain\nin-toto-verify --layout root.layout \\\n  --layout-key keys\u002Fowner.pub \\\n  --link-dir .\u002Flink-metadata\u002F\n\n# If verification passes, proceed with deployment\nif [ $? -eq 0 ]; then\n  kubectl apply -f deployment.yaml\n  echo \"Supply chain verification passed - deploying\"\nelse\n  echo \"SUPPLY CHAIN VERIFICATION FAILED - blocking deployment\"\n  exit 1\nfi\n```\n\n### Step 5: Kubernetes Admission Control\n\nIntegrate with a policy engine to verify attestations at admission:\n\n```yaml\napiVersion: admissionregistration.k8s.io\u002Fv1\nkind: ValidatingWebhookConfiguration\nmetadata:\n  name: in-toto-verifier\nwebhooks:\n  - name: verify.in-toto.io\n    rules:\n      - apiGroups: [\"apps\"]\n        resources: [\"deployments\"]\n        operations: [\"CREATE\", \"UPDATE\"]\n    clientConfig:\n      service:\n        name: in-toto-webhook\n        namespace: security\n        path: \u002Fverify\n    failurePolicy: Fail\n    sideEffects: None\n    admissionReviewVersions: [\"v1\"]\n```\n\n## SLSA Integration\n\nin-toto attestations map directly to SLSA (Supply chain Levels for Software Artifacts) requirements:\n\n| SLSA Level | in-toto Requirement |\n|------------|-------------------|\n| Level 1 | Build process documented (layout exists) |\n| Level 2 | Signed attestations from hosted build service |\n| Level 3 | Hardened build platform, non-falsifiable provenance |\n| Level 4 | Two-party review, hermetic builds |\n\n## References\n\n- [in-toto Official Website](https:\u002F\u002Fin-toto.io\u002F)\n- [in-toto GitHub Repository](https:\u002F\u002Fgithub.com\u002Fin-toto\u002Fin-toto)\n- [CNCF in-toto Graduation Announcement](https:\u002F\u002Fwww.cncf.io\u002Fannouncements\u002F2025\u002F04\u002F23\u002Fcncf-announces-graduation-of-in-toto-security-framework-enhancing-software-supply-chain-integrity-across-industries\u002F)\n- [SLSA Framework](https:\u002F\u002Fslsa.dev\u002F)\n- [Sigstore Integration](https:\u002F\u002Fwww.sigstore.dev\u002F)\n",{"name":5,"tags":25,"author":35,"domain":36,"license":15,"version":37,"nist_csf":38,"subdomain":31,"description":7,"mitre_attack":43},[26,27,28,29,30,31,32,33,34],"in-toto","supply-chain-security","attestation","slsa","sigstore","container-security","cncf","provenance","sbom","mahipal","cybersecurity","1.0",[39,40,41,42],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01",[44,45,46,47,48],"T1610","T1611","T1609","T1525","T1195","main","8a3b3de73262a4c4db64523949360f3c599c2fb1","Anthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-supply-chain-security-with-in-toto",0,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use","https:\u002F\u002Fgithub.com\u002FSaiVatsal","https:\u002F\u002Fsaivatsal.github.io\u002FPortfolio\u002F","The Longer It Takes The Stronger It Becomes ","2026-09-21 22:45:58",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add SaiVatsal\u002FSkills-I-Use --skill implementing-supply-chain-security-with-in-toto",{"tool":64,"command":65},"bunx","bunx skills add SaiVatsal\u002FSkills-I-Use --skill implementing-supply-chain-security-with-in-toto",{"tool":67,"command":68},"pnpm","pnpm dlx skills add SaiVatsal\u002FSkills-I-Use --skill implementing-supply-chain-security-with-in-toto","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-supply-chain-security-with-in-toto\u002FSKILL.md",true,[72,78,82,88,92,96,102],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"assets\u002Ftemplate.md","ASSET","资产文件",1356,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-supply-chain-security-with-in-toto\u002Fassets\u002Ftemplate.md",{"path":79,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fapi-reference.md","REFERENCE","参考文档",4813,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-supply-chain-security-with-in-toto\u002Freferences\u002Fapi-reference.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fstandards.md",2200,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-supply-chain-security-with-in-toto\u002Freferences\u002Fstandards.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fworkflows.md",2826,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-supply-chain-security-with-in-toto\u002Freferences\u002Fworkflows.md",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fagent.py","SCRIPT","脚本",9843,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-supply-chain-security-with-in-toto\u002Fscripts\u002Fagent.py",{"path":103,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fprocess.py",10034,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-supply-chain-security-with-in-toto\u002Fscripts\u002Fprocess.py",[107,115,123,132,139,146],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":20},"01M7DJZP6E6KMBQV4CZSDPZEZ8","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":20},"01M7DJZFTS5TS06K2TV3MDTE67","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":20},"01M7DJRK4SRQ908F2TJM6EZ7EV","ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","MIT","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":20},"01M7DJR902059VEQP23PVM2WA0","design","Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social\u002Fads\u002Fweb\u002Fprint), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":20},"01M7DJR56QF5N6XYTCPCFHFMNP","design-system","Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing\u002Ftypography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign-system\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":20},"01M7DJQXB6M0SFF7NX8J5N01AH","banner-design","Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter\u002FX, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fbanner-design\u002FSKILL.md",[],[]]