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.

SHAMAN-KATHMANDU/ims

https://github.com/SHAMAN-KATHMANDU/ims · scanned 2026-06-16 00:09 UTC (2 months, 2 weeks ago)

364 raw signals (45 security + 319 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 293 actionable findings from 2 signal sources. 202 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 · 285 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 7 High 18 Medium 41 Low 106 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 285 Crowd 0 Layer: Quality 100 Security 25 Cicd 7 Frontend 104 Network 1 Hardware 2 Api 54

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 `isLegacy` in apps/tenant-site/components/blocks/Ed…

View all legacy markers findings →

Commented-out code 53 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 (12 lines) in apps/api/tests/security/dangerous-permission…
info Commented-code block (5 lines) in apps/api/tests/integration/api/permissions-rb…
info Commented-code block (5 lines) in apps/api/prisma/seeds/index.ts:346
info Commented-code block (6 lines) in apps/api/prisma/seeds/cleanup.test.ts:20
info Commented-code block (5 lines) in apps/api/prisma/seeds/30-rbac-roles-permissio…
info Commented-code block (7 lines) in apps/api/prisma/seeds/essential/02-site-templ…
info Commented-code block (8 lines) in apps/api/src/config/router.config.ts:134
info Commented-code block (5 lines) in apps/api/src/modules/blog/blog.repository.ts:…
info Commented-code block (5 lines) in apps/api/src/modules/inventory/inventory.repo…
info Commented-code block (5 lines) in apps/api/src/modules/website-orders/website-o…
info Commented-code block (5 lines) in apps/api/src/modules/pages/pages.repository.t…
info Commented-code block (5 lines) in apps/api/src/modules/pages/pages.repository.t…

View all commented-out code findings →

Config drift 16 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

low Stray `console.log` in TS/JS — apps/api/prisma/seeds/essential/04-backfill-site…
low Stray `console.log` in TS/JS — apps/api/src/config/env.ts:172
low Node manifest has dependencies but no lockfile: packages/eslint-config/package.… packages/eslint-config/package.json
high Agent instruction/config may expose a secret: .cursor/rules/feature-lock-archit… .cursor/rules/feature-lock-architecture.mdc:54
high Agent instruction/config may expose a secret: .cursor/rules/frontend-architectu… .cursor/rules/frontend-architecture.mdc:197
high Agent instruction/config may expose a secret: .cursor/skills/security-scan/SKIL… .cursor/skills/security-scan/SKILL.md:57
high Agent instruction/config may expose a secret: .cursor/skills/e2e-testing/SKILL.… .cursor/skills/e2e-testing/SKILL.md:349
high Agent instruction/config may expose a secret: .cursor/skills/api-design/SKILL.md .cursor/skills/api-design/SKILL.md:306
high Agent instruction/config may expose a secret: .cursor/skills/postgres-patterns/… .cursor/skills/postgres-patterns/SKILL.md:319
high Agent instruction/config may expose a secret: .cursor/skills/backend-patterns/S… .cursor/skills/backend-patterns/SKILL.md:233
high Agent instruction/config may expose a secret: .cursor/skills/docker-patterns/SK… .cursor/skills/docker-patterns/SKILL.md:141
high Agent instruction/config may expose a secret: .cursor/skills/deployment-pattern… .cursor/skills/deployment-patterns/SKILL.md:168

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/aa3952c3-16e4-4781-adb3-86c884b4dbe3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/aa3952c3-16e4-4781-adb3-86c884b4dbe3/

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.