Compliance Standards

Validates software repositories against OpenSSF Scorecard, CII Best Practices, OWASP Top 10, and SOC2 frameworks.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/nsalvacao/nsalvacao-claude-code-plugins --skill compliance-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Compliance Standards
Source: https://github.com/nsalvacao/nsalvacao-claude-code-plugins/tree/main/plugins/repo-structure/skills/compliance-standards
Command: npx skills add https://github.com/nsalvacao/nsalvacao-claude-code-plugins --skill compliance-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates software repositories against major security and governance frameworks such as OpenSSF Scorecard, CII Best Practices, OWASP Top 10, and SOC2.

Core Features & Use Cases

  • OpenSSF Scorecard checks with per-check scoring and an overall status to guide security posture.
  • CII Best Practices badge alignment with public version control, issue tracking, build/test instructions, and automated vulnerability reporting signals.
  • OWASP Top 10 risk validation and guidance for remediation planning across projects.
  • SOC2 control mapping and evidence collection to support governance and audit readiness.

Quick Start

Run the compliance checks across your repository to produce an audit-ready report.

Frequently Asked Questions about Compliance Standards

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

FAQPage Schema
How do I check my repository against OpenSSF Scorecard and CII Best Practices?

To check repository compliance, run automated checks against OpenSSF Scorecard and CII Best Practices frameworks. The process evaluates per-check scoring, version control, issue tracking, and automated vulnerability reporting to generate an audit-ready compliance status.

How do I validate OWASP Top 10 risks in my open-source project?

Validate OWASP Top 10 risks by applying automated checks to your software repositories. The process performs risk validation and generates structured reporting with guidance for remediation planning across your open-source or enterprise projects.

Can I use this to collect SOC2 audit evidence for governance readiness?

Yes, you can collect SOC2 audit evidence by mapping controls and generating structured reports. The checks support evidence collection for governance and audit readiness, enabling downstream tooling to consume the compliance data.

Does the compliance validation process support script-based checks for CI pipelines?

The compliance validation process supports script-based checks such as scripts/check-cii-compliance.sh. These scripts enable automated evidence collection and badge generation, integrating compliance validation into CI pipelines for structured reporting.

What is the best way to generate an audit-ready compliance report for multiple frameworks?

The best way to generate an audit-ready report is running automated checks across OpenSSF, CII, OWASP, and SOC2 frameworks simultaneously. This applies per-check scoring and control mapping to produce structured reporting for downstream governance tooling.

Do I need a specific environment to run CII Best Practices badge alignment checks?

You need an environment capable of executing script-based checks like scripts/check-cii-compliance.sh and accessing the repository's version control and issue tracking. The checks validate build/test instructions and automated vulnerability reporting signals.