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.

getsentry/sentry-docs

https://github.com/getsentry/sentry-docs · scanned 2026-06-16 04:24 UTC (2 months ago)

11 raw signals (0 security + 11 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months ago · v1 · 11 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 11 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

Exclude dismissed / FP Exclude test files

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

Showing 8 of 11 actionable findings. 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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: SKILL.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

SKILL.md VerificationSkill file

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing ci, operator-readme. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.

Repo hardeningGenerated repo pattern

low System graph 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: `CI`, `CODECOV_TOKEN`, `DEVELOPER_DOCS`, `NEXT_PUBLIC_DEVELOPER_DOCS`, `NEXT_TYPEGEN`, `NODE_ENV`, `SENTRY_AUTH_TOKEN`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: ci, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — redirects.js:2424

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph quality Complexity conf 1.00 Very large file: middleware.ts (4480 lines)

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

low System graph quality Complexity conf 1.00 Very large file: redirects.js (2434 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/fd403ecd-4183-4483-9df7-90543124260d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fd403ecd-4183-4483-9df7-90543124260d/

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.