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.

cloudposse/atmos

https://github.com/cloudposse/atmos · scanned 2026-06-17 01:53 UTC (1 month, 1 week ago)

225 raw signals (0 security + 225 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 143 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 13 High 8 Medium 54 Low 64 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 143 Crowd 0 Layer: Frontend 11 Network 4 Hardware 13 Security 32 Cicd 5 Quality 78

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 3 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

3 matching findings on this repo

info Commented-code block (5 lines) in website/plugins/docusaurus-plugin-llms-txt/sr…
info Commented-code block (5 lines) in website/plugins/docusaurus-plugin-llms-txt/sr…
info Commented-code block (5 lines) in website/plugins/doc-release-data/index.js:188

View all commented-out code findings →

Config drift 11 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

11 matching findings on this repo

critical Possible secret in pkg/ai/agent/base/config_test.go pkg/ai/agent/base/config_test.go:57
critical Possible secret in website/docusaurus.config.js website/docusaurus.config.js:386
low Very large file: pkg/config/load_test.go (1885 lines)
low Very large file: pkg/config/load.go (1523 lines)
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: agent-skills/skills/atmos-config/… agent-skills/skills/atmos-config/SKILL.md:284
medium Agent authority lacks a verifier contract: agent-skills/skills/atmos-config/SKI… agent-skills/skills/atmos-config/SKILL.md
high Agent instruction/config may expose a secret: agent-skills/skills/atmos-auth/SK… agent-skills/skills/atmos-auth/SKILL.md:165
high Agent instruction/config may expose a secret: agent-skills/skills/atmos-gitops/… agent-skills/skills/atmos-gitops/SKILL.md:135
high Agent instruction/config may expose a secret: agent-skills/skills/atmos-terrafo… agent-skills/skills/atmos-terraform/SKILL.md:261
high Agent instruction/config may expose a secret: agent-skills/skills/atmos-stores/… agent-skills/skills/atmos-stores/SKILL.md:100

View all config drift findings →

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/78aea77f-c859-418a-a827-7225ffa40b0a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/78aea77f-c859-418a-a827-7225ffa40b0a/

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.