ivnovomi/NYXOR Audit
Run a NYXOR security audit (DNS + TLS + HTTP, SSL-Labs-style letter grade) against a domain, entirely on GitHub-hosted runners. No server, no PyPI publish, no account to sign up for.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| target | Domain to audit (e.g. example.com) | yes | — |
| report-path | Path to write the report to. Format is inferred from the extension (.json, .md, .html, .sarif — pipe .sarif into github/codeql-action/upload-sarif for GitHub Security tab alerts). Leave empty to skip writing a report. | no | nyxor-report.html |
| badge-path | Path to write the SVG grade badge to. Leave empty to skip. | no | nyxor-badge.svg |
| unsafe | Allow NyxScript's python:/pip escape hatches (not used by this action itself). | no | false |
| nyxor-ref | Git ref of ivnovomi/nyxor to install (branch, tag, or commit). | no | main |
| pr-comment | Post the grade as a comment on the pull request this action ran on. Only fires on `pull_request` events; the calling workflow needs `permissions: pull-requests: write`. No-op otherwise. | no | true |
| fail-on | Severity to gate on (critical, high, medium, low, or info). Leave empty (the default) to skip the check entirely. This action never fails itself over findings — a composite action failing partway loses its own outputs, which would take `grade` down with it. Check the `exceeded-fail-on` output in your own workflow instead (see the README for the one-line pattern); reports/badges/PR comments get written either way regardless of what you do with it. | no | "" |
Outputs
| name | description |
|---|---|
| grade | Letter grade (A+ down to F). |
| exceeded-fail-on | "true" if `fail-on` was set and a finding met or exceeded it, "false" otherwise (including when `fail-on` was left empty). |