security-openssf

Automate OpenSSF Scorecard GitHub Action installation and remediation.

7|Updated May 28, 2026
One-click install
npx skills add https://github.com/zcaceres/skills --skill security-openssf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-openssf
Source: https://github.com/zcaceres/skills/tree/main/skills/security-openssf
Command: npx skills add https://github.com/zcaceres/skills --skill security-openssf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, gh, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill solves the problem of insecure or poorly configured supply-chain security by automating the setup of the OpenSSF Scorecard GitHub Action with a safe, two-phase rollout that prevents premature public exposure of low security scores.

Core Features & Use Cases

  • Two-Phase Rollout: Installs the Scorecard action in a private-first mode (publish_results: false) to allow for internal triage before going public.
  • Remediation Planning: The fix subcommand analyzes Scorecard findings and generates a bucketed plan to address file-based and settings-based security issues.
  • Use Case: A developer wants to improve their repository's security posture but fears a low initial score on the public scorecard.dev dashboard; this skill allows them to identify and fix issues privately before opting into public reporting.

Quick Start

Run the security-openssf skill to scaffold the OpenSSF Scorecard action in your repository.

Frequently Asked Questions about security-openssf

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

FAQPage Schema
How do I automate OpenSSF Scorecard setup without exposing a low initial security score publicly?

Automate OpenSSF Scorecard setup using a safe, two-phase rollout that initially publishes results privately (publish_results: false). This allows for internal triage and remediation of security findings before opting into public scorecard.dev dashboard reporting.

How do I generate a remediation plan from OpenSSF Scorecard SARIF reports?

Generate a remediation plan from OpenSSF Scorecard SARIF reports by running the fix subcommand. It analyzes the SARIF findings and generates a bucketed plan to address both file-based and settings-based supply-chain security issues in the repository.

Do I need the GitHub CLI and jq to automate OpenSSF supply-chain security workflows?

Yes, you need both the GitHub CLI (gh) and jq to automate OpenSSF supply-chain security workflows. These dependencies are required for processing SARIF report artifacts and managing target repository settings and workflow configurations.

What is the best way to roll out OpenSSF Scorecard GitHub Actions across public repositories?

The best way to roll out OpenSSF Scorecard GitHub Actions is a two-phase approach: install the action in a private-first mode for internal triage, remediate file and settings issues, then enable public reporting to safely improve supply-chain security posture.

Can I manage repository security policy enforcement and workflow configuration for OpenSSF Scorecard automatically?

Yes, you can automatically manage repository security policy enforcement and workflow configuration for OpenSSF Scorecard. The automation targets public repositories to configure workflows, analyze SARIF reports, and enforce security settings.

Why does the security-openssf automation use a private-first mode for Scorecard results?

The security-openssf automation uses a private-first mode to prevent premature public exposure of low security scores. It allows developers to identify and fix supply-chain vulnerabilities privately before opting into the public scorecard.dev reporting.