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

JKHeadley/instar

https://github.com/JKHeadley/instar · scanned 2026-05-15 20:53 UTC (4 weeks ago) · 10 languages

779 raw signals (209 security + 570 graph) 7th percentile · Typescript · huge (>500K LoC) System graph score 70 (higher by 2)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
70.8
/100
Security checks
72
55 findings
System graph
70
100.0% cov · 0 findings
Critical
1
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-17-v4 calibration-aware
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 58.4 0.25 14.60
testing_score 95.0 0.20 19.00
documentation_score 69.6 0.15 10.44
practices_score 65.0 0.15 9.75
code_quality 54.8 0.10 5.48
Overall 1.00 72.0
Calibrated penalty buckets (security_score): web: 1.6 · agent: 3.2 · authz: 39.8 · docker: 1.2 · threat: 10.3 · journey: 5.4
Severity distribution — click a segment to filter
Active filters: severity: high × excluding tests × Reset all
Severity: Critical 1 High 39 Medium 5 Low 6 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 55 System graph 0 Crowd 0 Layer: Quality 11 Software 2 Security 39 Cicd 3
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Ranks in the 9th percentile among medium-sized repos. Strongest documentation (88), testing (85); weakest practices (37), security (40). 260 findings (124 critical, 6 high). Most common pattern: cpp-new-without-delete. ~74h tech debt (rating A).

Showing 39 of 55 actionable findings. 199 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high Security checks security secrets conf 0.85 48 occurrences Hardcoded secret in source
API key, AWS access key, password, or private key embedded directly in source. AI assistants frequently leak demo creds.
12 files, 47 locations
tests/unit/ContentClassifier.test.ts:85, 104, 113, 135, 145, 154, 163, 356, +2 more (10 hits)
tests/unit/PolicyEnforcementLayer.test.ts:80, 91, 100, 108, 147, 154, 386, 399, +1 more (9 hits)
tests/unit/secret-redactor.test.ts:54, 57, 61, 82, 105 (5 hits)
tests/e2e/security-pipeline-e2e.test.ts:96, 1335, 1358, 1423 (4 hits)
tests/unit/machine-identity.test.ts:53, 92, 343, 344 (4 hits)
tests/unit/serendipity-capture.test.ts:310, 316, 328, 335 (4 hits)
tests/e2e/security-lifecycle.test.ts:81, 95 (2 hits)
tests/unit/CoherenceGateE2E.test.ts:483, 486 (2 hits)
hardcoded-secret · CWE-798 · A07:2021
high Security checks security auth conf 0.70 [AUC003] Object-level route lacks visible authorization: A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: DELETE /semantic/forget/:id.
A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: DELETE /semantic/forget/:id.
src/server/routes.ts:2403
high Security checks security auth conf 0.70 [AUC003] Object-level route lacks visible authorization: A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: GET /context/:segmentId.
A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: GET /context/:segmentId.
src/server/routes.ts:3684
high Security checks security auth conf 0.70 [AUC003] Object-level route lacks visible authorization: A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: GET /internal/stop-gate/annotations/:eventId.
A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: GET /internal/stop-gate/annotations/:eventId.
src/server/routes.ts:1817
high Security checks security auth conf 0.70 [AUC003] Object-level route lacks visible authorization: A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: GET /memory/evidence/by-entity/:id.
A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: GET /memory/evidence/by-entity/:id.
src/server/routes.ts:2610
high Security checks security auth conf 0.70 [AUC003] Object-level route lacks visible authorization: A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: GET /moltbridge/trust/:agentId.
A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: GET /moltbridge/trust/:agentId.
src/moltbridge/routes.ts:73
high Security checks security auth conf 0.70 [AUC003] Object-level route lacks visible authorization: A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: GET /semantic/explore/:id.
A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: GET /semantic/explore/:id.
src/server/routes.ts:2474
high Security checks security auth conf 0.70 [AUC003] Object-level route lacks visible authorization: A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: GET /semantic/recall/:id.
A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: GET /semantic/recall/:id.
src/server/routes.ts:2392
high Security checks security auth conf 0.70 [AUC003] Object-level route lacks visible authorization: A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: POST /backups/:id/restore.
A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: POST /backups/:id/restore.
src/server/routes.ts:2157
high Security checks security auth conf 0.70 [AUC003] Object-level route lacks visible authorization: A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: POST /jobs/:slug/trigger.
A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: POST /jobs/:slug/trigger.
src/server/routes.ts:4541
high Security checks security auth conf 0.70 [AUC003] Object-level route lacks visible authorization: A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: POST /semantic/verify/:id.
A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: POST /semantic/verify/:id.
src/server/routes.ts:2486
high Security checks security auth conf 0.74 [AUC002] Low visible authorization coverage in route inventory: Only 22.5% of discovered routes show nearby authentication, authorization, middleware, or public-route evidence.
Only 22.5% of discovered routes show nearby authentication, authorization, middleware, or public-route evidence.
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: GET /backups.
An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: GET /backups.
src/server/routes.ts:2136
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: GET /git/log.
An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: GET /git/log.
src/server/routes.ts:2260
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: GET /git/status.
An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: GET /git/status.
src/server/routes.ts:2200
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: GET /health.
An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: GET /health.
src/server/routes.ts:1091
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: POST /backups.
An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: POST /backups.
src/server/routes.ts:2146
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: POST /gh-check/verify-nonce.
An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: POST /gh-check/verify-nonce.
src/server/worktreeRoutes.ts:245
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: POST /git/commit.
An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: POST /git/commit.
src/server/routes.ts:2211
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: POST /git/pull.
An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: POST /git/pull.
src/server/routes.ts:2248
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: POST /git/push.
An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: POST /git/push.
src/server/routes.ts:2225
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: POST /worktrees/resolve.
An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: POST /worktrees/resolve.
src/server/worktreeRoutes.ts:108
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: DELETE /semantic/forget/:id.
A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: DELETE /semantic/forget/:id.
src/server/routes.ts:2403
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: GET /dashboard.
A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: GET /dashboard.
src/server/AgentServer.ts:207
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /api/handoff/request.
A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /api/handoff/request.
src/server/machineRoutes.ts:150
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /backups/:id/restore.
A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /backups/:id/restore.
src/server/routes.ts:2157
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /dashboard/unlock.
A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /dashboard/unlock.
src/server/AgentServer.ts:223
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /homeostasis/pause.
A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /homeostasis/pause.
src/server/routes.ts:2000
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /homeostasis/reset.
A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /homeostasis/reset.
src/server/routes.ts:2006
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /moltbridge/profile/approve.
A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /moltbridge/profile/approve.
src/moltbridge/routes.ts:178
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /reflection/session-start.
A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /reflection/session-start.
src/server/routes.ts:1967
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: PUT /homeostasis/thresholds.
A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: PUT /homeostasis/thresholds.
src/server/routes.ts:2011
high Security checks quality Quality conf 0.72 Agent control bridge may listen on a network interface without visible auth
Agent, MCP, sidecar, and command bridge servers often start as local helpers. Binding them to 0.0.0.0 or a default all-interface listener without an authorization guard can expose tool execution or session data to the LAN.
src/core/FeedbackManager.ts:69
high Security checks quality Quality conf 0.72 Agent control bridge may listen on a network interface without visible auth
Agent, MCP, sidecar, and command bridge servers often start as local helpers. Binding them to 0.0.0.0 or a default all-interface listener without an authorization guard can expose tool execution or session data to the LAN.
src/core/DispatchManager.ts:135
high Security checks security auth conf 0.82 2 occurrences Browser storage is used for session token material
localStorage and sessionStorage are readable by injected JavaScript. For sensitive sessions, this turns XSS into account compromise.
lines 3305, 3325
dashboard/index.html:3305, 3325 (2 hits)
high Security checks security Crypto conf 0.45 32 occurrences Crypto — plaintext HTTP for sensitive endpoint
Hardcoded http:// (not localhost) for endpoints that handle credentials or data.
12 files, 27 locations
tests/unit/git-sync-transport.test.ts:62, 362, 368, 374, 381, 390 (6 hits)
tests/integration/execution-journal-lifecycle.test.ts:123, 160, 177, 210 (4 hits)
tests/integration/messaging-routes.test.ts:292, 326, 364, 393 (4 hits)
tests/unit/ExecutionJournal.test.ts:87, 99, 516 (3 hits)
tests/unit/message-router.test.ts:280, 315, 346 (3 hits)
tests/e2e/discernment-layer-e2e.test.ts:674
tests/e2e/launchd-node-boot-wrapper.test.ts:444
tests/e2e/messaging-lifecycle.test.ts:203
http-not-https · CWE-319 · A02:2021
high Security checks cicd CI/CD security conf 0.82 Docker final stage has no non-root USER
Docker images run as root unless the image or Dockerfile switches to a non-root user.
Dockerfile.relay:26 CI/CD securitycontainers
high Security checks quality Quality conf 0.74 Frontend API reference is not matched by discovered backend routes
A frontend string references a same-origin API path that Repobility could not match to backend route inventory. This often causes live 404s in user journeys.
src/core/PostUpdateMigrator.ts:1604
high Security checks software Logging conf 0.85 5 occurrences PII printed to stdout/stderr
Logging password/token/email/ssn directly to stdout.
lines 52, 55, 57, 97, 214
src/cli.ts:52, 55, 57, 97, 214 (5 hits)
print-pii · CWE-532 · A09:2021
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/00f3e9b4-a692-4d73-b1d2-2e06abed64cd/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/00f3e9b4-a692-4d73-b1d2-2e06abed64cd/

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.