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.

SidCorp-co/forge

https://github.com/SidCorp-co/forge · scanned 2026-06-16 00:12 UTC (2 months, 2 weeks ago)

958 raw signals (0 security + 958 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 940 actionable findings from 1 signal source. 18 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 940 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 495 Medium 47 Low 74 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 940 Crowd 0 Layer: Frontend 75 Hardware 4 Security 17 Cicd 4 Quality 295 Api 545

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.

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low Old/deprecated-named symbol `toLegacy` in packages/tests/web/features/activity/…

View all legacy markers findings →

Commented-out code 251 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/`.

12 matching findings on this repo

info Commented-code block (11 lines) in scripts/check-source-language.mjs:8
info Commented-code block (5 lines) in packages/web-v2/next.config.ts:27
info Commented-code block (5 lines) in packages/web-v2/scripts/gen-help-content.mjs:2
info Commented-code block (5 lines) in packages/web-v2/src/design/patterns/page-cont…
info Commented-code block (7 lines) in packages/web-v2/src/design/patterns/screen-ta…
info Commented-code block (5 lines) in packages/web-v2/src/design/patterns/markdown.…
info Commented-code block (5 lines) in packages/web-v2/src/providers/auth-provider.t…
info Commented-code block (7 lines) in packages/web-v2/src/app/layout.tsx:40
info Commented-code block (5 lines) in packages/web-v2/src/app/invite/accept/page.ts…
info Commented-code block (7 lines) in packages/web-v2/src/app/(workspace)/layout.ts…
info Commented-code block (5 lines) in packages/web-v2/src/app/(workspace)/projects/…
info Commented-code block (8 lines) in packages/web-v2/src/lib/api/error.ts:36

View all commented-out code findings →

Config drift 28 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.

12 matching findings on this repo

medium Insecure pattern 'cors_wildcard' in packages/web-v2/src/app/forge-config/route.… packages/web-v2/src/app/forge-config/route.ts:44
info Commented-code block (5 lines) in packages/web-v2/next.config.ts:27
info Commented-code block (6 lines) in packages/tests/web/features/pipeline/session-…
info Commented-code block (6 lines) in packages/dev/vitest.config.ts:15
info Commented-code block (7 lines) in packages/core/vitest.integration.config.ts:6
info Commented-code block (5 lines) in packages/core/tests/integration/pipeline-per-…
info Commented-code block (5 lines) in packages/core/src/config/env.ts:75
info Commented-code block (7 lines) in packages/core/src/pipeline/pipeline-config-se…
info Commented-code block (6 lines) in packages/core/src/pipeline/pipeline-config-sc…
info Commented-code block (9 lines) in packages/core/src/pipeline/pipeline-config-se…
high Dangling fetch: PATCH /api/projects/${projectId}/pipeline-config (packages/core…
high Dangling fetch: PATCH /api/projects/${projectId}/pipeline-config (packages/core…

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/f66b742e-7be1-4d10-96c5-30c79e2c6103/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f66b742e-7be1-4d10-96c5-30c79e2c6103/

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.