openops-cloud/openops — Repobility public scan

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.

Sign up free Scan another repo

openops-cloud/openops

https://github.com/openops-cloud/openops · scanned 2026-05-16 12:50 UTC (1 day, 8 hours ago) · 10 languages

259 findings (9 legacy + 250 scanner) 2/10 scanners ran 95th percentile · Typescript · large (100-500K LoC) Scanner says 56 (higher by 29)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 3 days ago · v1 · 253 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

100.0% cov · 250 gaps

click to filter

{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}

Severity distribution — click a segment to filter

Active filters: layer: quality × excluding tests × Reset all

Scan summary Repository scanned at 55.8/100 with 100.0% coverage. It contains 7818 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 250 findings — concentrated in frontend (82), software (50), api (50). Risk profile is high: 0 critical, 7 high, 34 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 15 of 253 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium 9-layer quality integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/blocks/cloudhealth/src/lib/common/execute-graphql-query.ts:16

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

integrityfragile-runtimerobustness

medium 9-layer quality integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/blocks/imap/src/lib/common/fetch-emails.ts:45

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

integrityfragile-runtimerobustness

medium 9-layer quality integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/engine/src/get-environment-id.ts:7

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

integrityfragile-runtimerobustness

medium 9-layer quality integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/engine/src/get-feature-flag.ts:10

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

integrityfragile-runtimerobustness

medium 9-layer quality integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/engine/src/lib/handler/context/engine-constants.ts:230

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

integrityfragile-runtimerobustness

medium 9-layer quality integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/engine/src/lib/services/files.service.ts:121

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

integrityfragile-runtimerobustness

medium 9-layer quality integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/engine/src/lib/services/storage.service.ts:66

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

integrityfragile-runtimerobustness

medium 9-layer quality integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/openops/src/lib/aws/azure-aws-federation.ts:103

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

integrityfragile-runtimerobustness

medium 9-layer quality integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/server/api/src/app/blocks/block-sync-service.ts:123

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

integrityfragile-runtimerobustness

medium 9-layer quality integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/ui-components/src/stories/markdown.stories.tsx:395

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

integrityfragile-runtimerobustness

medium 9-layer quality integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — tools/scripts/sync-models.ts:276

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

integrityfragile-runtimerobustness

low 9-layer quality maintenance conf 1.00 42 TODO/FIXME markers

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

maintenance

low 9-layer quality integrity conf 1.00 7 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `AWS_LAMBDA_FUNCTION_NAME`, `NODE_ENV`, `OPS_BASE_CODE_DIRECTORY`, `OPS_CODE_SANDBOX_TYPE`, `OPS_FINOPS_BENCHMARK_ENABLED`, `TZ`, `VITE_OPS_BACKEND_URL`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

integrityconfig-drift

low 9-layer quality complexity conf 1.00 Very large file: packages/server/api/test/integration/ce/flows/flow.test.ts (1551 lines)

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

complexity

low 9-layer quality complexity conf 1.00 Very large file: packages/shared/test/flow/flow-helper.test.ts (3953 lines)

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

complexity

{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}

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/48fc393f-1836-47d4-82d1-6e5622dc46fc/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/48fc393f-1836-47d4-82d1-6e5622dc46fc/

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.