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.

dichovsky/atlassian-api-client

https://github.com/dichovsky/atlassian-api-client · scanned 2026-06-17 01:56 UTC (1 month, 1 week ago)

73 raw signals (0 security + 73 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 3 findings
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.
3 matching findings on this repo
  • low Old/deprecated-named symbol `listLegacy` in src/cli/commands/jira.ts:672
  • low Old/deprecated-named symbol `listLegacy` in src/jira/resources/projects.ts:372
  • low Old/deprecated-named symbol `listLegacy` in test/jira/projects.test.ts:273
View all legacy markers findings →
Commented-out code 41 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 (6 lines) in scripts/generate-codemap.js:392
  • info Commented-code block (6 lines) in src/skill-installer/index.ts:141
  • info Commented-code block (6 lines) in src/confluence/resources/comments.ts:138
  • info Commented-code block (6 lines) in src/confluence/resources/spaces.ts:505
  • info Commented-code block (5 lines) in src/confluence/resources/custom-content.ts:127
  • info Commented-code block (12 lines) in src/core/pagination.ts:323
  • info Commented-code block (5 lines) in src/core/cache.ts:71
  • info Commented-code block (7 lines) in src/core/connect-jwt.ts:86
  • info Commented-code block (7 lines) in src/core/transport.ts:96
  • info Commented-code block (6 lines) in src/core/batch.ts:87
  • info Commented-code block (9 lines) in src/core/config.ts:89
  • info Commented-code block (8 lines) in src/core/request.ts:62
View all commented-out code findings →
Config drift 2 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.
2 matching findings on this repo
  • info Commented-code block (9 lines) in src/core/config.ts:89
  • info Commented-code block (5 lines) in test/cli/config.test.ts:331
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/0270e24c-9fdb-4f65-afcf-ef47aa5aa34f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0270e24c-9fdb-4f65-afcf-ef47aa5aa34f/

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.