hyperpolymath/Validate K9 Configurations
Scan and validate K9 configuration files (.k9 and .k9.ncl) in your repository. Checks for K9! magic number, pedigree block (name, version, security_level), valid security levels (kennel/yard/hunt), and ensures hunt-level files include a signature field.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| path | Directory path to scan for K9 files. Defaults to the repository root. | no | . |
| strict | When true, warnings are promoted to errors and the action will fail on any validation issue. Defaults to false. | no | false |
| paths-ignore | Newline-separated path fragments to skip. Each line is matched as a substring against the file's path. Defaults to common vendored / training-corpus / fixture patterns so consumers don't have to repeat this carve-out in every repo. Pass an empty string to disable. Pattern follows hyperpolymath/hypatia#243 — validators that scan content patterns must distinguish a target file from a fixture / vendored / training-corpus file that legitimately contains the pattern being checked. The vendored-estate-clone carve-out (e.g. absolute-zero/) follows the convention that a tracked subdirectory named after an upstream hyperpolymath repo is a vendored copy whose K9 files belong to the upstream's CI, not the host's. | no | vendor/ vendored/ verified-container-spec/ .audittraining/ integration/fixtures/ test/fixtures/ tests/fixtures/ absolute-zero/ |
Outputs
| name | description |
|---|---|
| files-scanned | Number of K9 files scanned |
| errors | Number of validation errors found |
| warnings | Number of validation warnings found |