A plugin providing a subagent to scan a source code project for potential FIPS compliance issues
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin that provides comprehensive FIPS 140-3 compliance auditing for containerized applications running on Red Hat Enterprise Linux 9 (or later).
This plugin helps ensure your applications meet FIPS 140-3 cryptographic compliance requirements by:
Add this plugin directly via Git URL:
# SSH
/plugin add [email protected]:grdryn/fips-compliance-checker-claude-code-plugin.git
# HTTPS
/plugin add https://github.com/grdryn/fips-compliance-checker-claude-code-plugin
If a marketplace includes this plugin, install via:
/plugin install fips-compliance-checker@<marketplace-name>
The Python scanner uses Bandit in a containerized environment and requires one of the following container runtimes:
Podman (recommended for RHEL/Fedora):
dnf install podman
Docker:
# See https://docs.docker.com/get-docker/
On first run, the scanner will automatically pull the Bandit container image (ghcr.io/pycqa/bandit/bandit:latest, ~50MB).
Air-gapped environments: Pre-pull the image and ensure it's available in your local registry:
podman pull ghcr.io/pycqa/bandit/bandit:latest
# or
docker pull ghcr.io/pycqa/bandit/bandit:latest
Use the fully-qualified /fips-compliance-checker:fips-scan command for direct invocation:
# Scan the current project
/fips-compliance-checker:fips-scan
# Scan a specific container image
/fips-compliance-checker:fips-scan quay.io/myorg/myapp:v1.2.3
Note: Claude Code CLI currently requires the fully-qualified format /plugin-name:command-name.
The agent will automatically activate when you ask FIPS-related questions:
The agent proactively activates when you mention:
requirements.txt, Pipfile (Python)go.mod, go.sum (Go)Cargo.toml, Cargo.lock (Rust)pom.xml, build.gradle (Java)package.json (Node.js)CMakeLists.txt, Makefile (C/C++)By default, the scanner excludes non-production code from analysis to focus on actual runtime compliance issues. The following patterns are automatically excluded:
*/tests/* - Test directories*/test_*.py - Test file prefix pattern*/*_test.py - Test file suffix pattern*/conftest.py - pytest configuration*/examples/*, */samples/* - Example code directories*/demo/*, */demos/* - Demo applications*/docs/examples/* - Documentation examples*/tutorials/* - Tutorial code*/playground/* - Experimental/playground code*/benchmarks/* - Benchmark code*/scripts/* - Utility scripts*/tools/* - Development tools*/utilities/* - Helper utilities*/venv/*, */.venv/*, */env/* - Virtual environments*/build/*, */dist/* - Build outputs*/__pycache__/*, */.eggs/* - Python cache*/node_modules/* - Node.js dependenciesYou can add additional exclusion patterns using the --exclude flag:
# Scan Python code with custom exclusions
cd scripts/python
./scan-python-fips.sh --exclude "*/vendor/*" --exclude "*/legacy/*"
Note: Custom exclusions are added to the default patterns (not replacing them).
npx claudepluginhub jeremyeder/ai-helpers-fixed --plugin fips-compliance-checkerAgent and skill evaluation harness with MLflow integration
Site generation skills for the OpenDataHub Skills Registry
Assess RFEs against quality criteria using a structured rubric
Orchestrator skills, agent prompts, and state management for the Jira autofix pipeline
Autonomous knowledge management skills for keeping AI context files up to date
Professional security tools for Claude Code: vulnerability scanning, compliance, cryptography audit, container & API security
Detects insecure default configurations including hardcoded credentials, fallback secrets, weak authentication defaults, and dangerous values in production
Open-source cybersecurity analysis agent. Scans any local project for vulnerabilities: code security (SAST), dependency CVEs (SCA), secret leaks, authentication/authorization flaws, cryptographic weaknesses, misconfigurations, supply chain risks, and CI/CD security. Covers all OWASP 2025 Top 10 and CWE Top 25 categories. Generates prioritized reports with remediation guidance. Invoke with /cyber-neo [path].
Audit and harden your software supply chain - packages, containers, GitHub Actions, IaC, AI/ML models, and IDE extensions. Action commands fix issues directly; walkthrough commands guide you through advanced setup.
Security compliance and vulnerability analysis tools for Go projects
Implements automated security scanning for dependencies, code, and containers using tools like Trivy, Snyk, and npm audit. Use when setting up CI/CD security gates, conducting pre-deployment audits, or meeting compliance requirements.