Run Bash-based production readiness audits with secret scanning and SBOM generation.
npx skills add https://github.com/adamos486/skills --skill production-ready-adamos486
Please help me install this Agent Skill. Skill: production-ready Source: https://github.com/adamos486/skills/tree/main/production-ready Command: npx skills add https://github.com/adamos486/skills --skill production-ready-adamos486
Production readiness is often a bottleneck before releasing software; this Skill automates the comprehensive checks required to verify security, compliance, and operational readiness, reducing manual toil and release risk.
Run the main orchestrator to perform a production readiness audit
High-intent search queries and answers about installing and using this skill.
You automate production readiness by running an orchestrated Bash script that executes secret scanning, vulnerability checks, and configuration hygiene. This generates an automated markdown security audit report under docs/reports, reducing manual toil and release risk.
An automated SBOM generation and vulnerability assessment workflow includes secret scanning, dependency checks, configuration validation, and CI/CD checks. It uses tools like syft for SBOM generation and grype for vulnerability assessment to ensure secure releases.
Yes, production readiness audits support diverse tech stacks by utilizing language-specific dependency checkers like npm, pip-audit, cargo-audit, govulncheck, and bundle-audit to validate project dependencies and identify vulnerabilities across different environments.
Yes, you can run a quick security check instead of a full audit by specifying a mode-based parameter. The orchestrator supports quick, security, and full modes, allowing project-specific customization for flexible pre-release validation.
The best way to scan for hardcoded secrets is using integrated tools like gitleaks and trufflehog within an orchestrated readiness check. This approach validates configuration hygiene and identifies sensitive data leaks before deployment.
You need to install jq and grype because the Bash-based orchestrator depends on them to process vulnerability data and generate automated reports. These dependencies are required to execute the comprehensive security checks and format the final output.
woohyun212Audit software supply chains with SCA scans, SLSA matrices, and SBOMs.
Logisoft-webScan code repositories for vulnerabilities in dependencies, secrets, and configurations.
lklimekScan Go, Rust, Python, and Node.js dependencies for known vulnerabilities.
limit5Map CVE entries to affected components in a Software Bill of Materials.
