glog-sca

Translate SARIF SCA findings into a non-destructive remediation plan.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/glogai/glog-skills --skill glog-sca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: glog-sca
Source: https://github.com/glogai/glog-skills/tree/main/glog-sca
Command: npx skills add https://github.com/glogai/glog-skills --skill glog-sca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The glog-sca skill enables conservative planning for software composition analysis by translating SARIF findings into a structured remediation plan without changing any source files, dependencies, or project configuration.

Core Features & Use Cases

  • Planning-only SCA workflows: reads SARIF output and dependency manifests to assess findings and propose non-destructive remediation.
  • Evidence-based prioritization: classifies findings as likely genuine, false positives, or needs manual review, based on SARIF rules and manifests.
  • Artifact generation: produces a detailed remediation plan file to .glog/glog-sca-remediation-plan.md for review.

Quick Start

Use the glog-sca skill to generate a remediation plan from a current project's SARIF output without touching code.

Frequently Asked Questions about glog-sca

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

FAQPage Schema
How do I generate a remediation plan from SARIF software composition analysis findings?

To generate a remediation plan from SARIF software composition analysis findings, use a conservative planning skill that reads SARIF output and dependency manifests to produce non-destructive remediation guidance. It evaluates lockfiles and build configuration without modifying any code or manifests.

What is conservative SCA planning for dependency risks?

Conservative SCA planning for dependency risks is the process of translating software composition analysis findings into structured remediation guidance. It classifies findings as genuine, false positives, or needing manual review based on SARIF rules and repository context.

Can I analyze dependency vulnerabilities without modifying source files or manifests?

Yes, you can analyze dependency vulnerabilities without modifying source files or manifests. This planning-only approach reads SARIF output and lockfiles to assess findings and outputs a detailed remediation plan file without touching project configuration.

Does SARIF-based SCA planning work with lockfiles and build configuration files?

SARIF-based SCA planning works with lockfiles and build configuration files by evaluating them alongside SARIF findings. It applies to OSS scanning workflows to assess dependency findings and generate actionable, non-destructive remediation guidance.

What's the best way to prioritize SARIF findings for manual review?

The best way to prioritize SARIF findings for manual review is using evidence-based classification that categorizes findings as likely genuine, false positives, or requiring manual review based on SARIF rules and dependency manifests.

What are the limitations of planning-only SCA workflows?

Limitations of planning-only SCA workflows include the inability to modify code or manifests and the requirement to clearly indicate uncertainty when evidence is insufficient. It generates a remediation plan file rather than automatically applying fixes.