Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

chronosphereio/terraform-provider-chronosphere

https://github.com/chronosphereio/terraform-provider-chronosphere · scanned 2026-06-17 01:49 UTC (1 month, 1 week ago)

16 raw signals (0 security + 16 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -2.1 (diff) · 12 actionable findings from 1 signal source. 4 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 12 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 7 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 12 Crowd 0 Layer: Network 2 Security 1 Cicd 2 Quality 7

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 74.6/100 with 77.8% coverage. It contains 2069 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 16 findings — concentrated in quality (7), cicd (6), network (2). Risk profile is low: 0 critical, 0 high, 9 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 12 of 12 actionable findings. 16 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned

hashicorp/setup-terraform@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

2 files, 3 locations

.github/workflows/codeql.yml:40, 50 (2 hits)

.github/workflows/ci.yml:37

CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in chronosphere/pkg/configunstable/swagger.json:8

Found a known-risky pattern (weak_hash). Review and replace if possible.

chronosphere/pkg/configunstable/swagger.json:8 Weak hash

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 37 placeholder/mock markers across 7 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

medium System graph network Security conf 1.00 Privileged port 18 in use

Port 18 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

scripts/go-build-ldflags.sh Ports

medium System graph network Security conf 1.00 Privileged port 58 in use

Port 58 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

scripts/go-build-ldflags.sh Ports

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

82 test file(s) for 1486 source file(s) (ratio 0.06). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Maintenance conf 1.00 266 TODO/FIXME markers

High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.

low System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/setup-go@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

2 files, 3 locations

.github/workflows/codeql.yml:31, 34 (2 hits)

.github/workflows/ci.yml:29

CI/CD securitySupply chainGithub actions

low System graph quality Docs conf 1.00 README lacks setup or run instructions

A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.

ReadmeRepo hardeningGenerated repo pattern

low System graph quality Complexity conf 1.00 Very large file: chronosphere/generated_resources.gen.go (2710 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

low System graph quality Complexity conf 1.00 Very large file: chronosphere/pagination/pagination.gen.go (2130 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/d4eaa4fb-b0a5-438c-beaa-94d164fa2bf3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d4eaa4fb-b0a5-438c-beaa-94d164fa2bf3/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.