Run a read-only cyber security audit and write a markdown report covering architecture, assets, CIA impact, code, supply chain, CI/CD, runtime, and AI-generated code.
HEAD
Current mutable ref · contents may change upstream
01
This is the entry file Smithers will copy for the selected workflow. Read it at the same ref shown above before trusting it.
.smithers/workflows/cyber-security-audit.tsxOpenworkflow source on GitHubThis page could not resolve an immutable commit. The link and install command follow HEAD, so review again if upstream changes.
02
Each repository source maps to a local destination. Installing fetches and copies this plan; it does not execute the files. Explicit support paths may not be fetched until installation, so verify them in GitHub too.
docs/cyber-security-audit.md.smithers/docs/cyber-security-audit.md.smithers/workflows/cyber-security-audit.tsxDestination.smithers/workflows/cyber-security-audit.tsx03
These lists answer different questions. Neither is a security audit, permission boundary, or guarantee of runtime behavior.
Claims written into the manifest by the publisher. They are self-reported and have not been verified.
Simple pattern matches in the entry file only. They can miss behavior in dependencies or flag harmless code.
04
Environment keys are names only. This directory never provides or validates their values.
None declared.
05
Documentation declared for this workflow is installed with the same workflow selection.
How to run the read-only security audit, scope active checks, and read the generated report.
.smithers/docs/cyber-security-audit.mdExample command
bunx smithers-orchestrator workflow run cyber-security-audit --input '{"repoPath":".","auditMode":"quick","allowActiveScanning":false}'