medium No recognized CI workflow discovered
Rule NO_CI · confidence medium · observed · .
Why it matters: No recognized CI configuration was found in the files scanned.
Fix: Verify your CI configuration and enforce required test gates.
PramanaSutra AI · QA & Release Audit · Markdown, HTML, JSON and SARIF are the same audit
missing-ci
Generated 2026-11-06T00:00:00.000Z · schema 1.0.0 · tool 0.3.4
3files inspected
1test files
0CI workflows
1findings
0critical + high
Tests executed by PramanaSutra: NO (static scan only). Executed-test results count only when supplied as evidence.
Supplied test evidence
No evidence file was supplied. Counts on this page are not test results. The release gate cannot treat the suite as passed.
Evidence binding: none. No evidence file was supplied.
Findings at a glance
| Severity | Rule | Where | Fix |
|---|---|---|---|
| medium | NO_CI | . | Verify your CI configuration and enforce required test gates. |
Findings
Test files seen
tests/a.test.js
CI workflows seen
None recognised (GitHub Actions, GitLab CI, Jenkins, Azure Pipelines, Bitbucket Pipelines, CircleCI, Buildkite, Drone, Woodpecker).
Release gate reasons
- No executed-test evidence supplied (use --evidence).
- No recognized CI workflow detected.
Capabilities
| Capability | State | What that means |
|---|---|---|
| staticAudit | executed | Source text was inspected with heuristic rules. |
| testExecution | not-run | not-run means this tool did not execute tests. evidence-supplied means an evidence file was attached. |
| browser | not-supported | No browser was launched. |
| securityScan | not-run | This is not a vulnerability scanner. |
| performanceTest | not-run | No load or timing test was run. |
| aiInference | not-run | The CLI did not call a model. |
Limitations
- Heuristic checks do not prove the absence of bugs or release readiness.
- No target tests, security scanners, browser, load tests or deploy checks were run by this tool.
- This report is decision support, not a compliance certification or legal advice.