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

dosco/graphjin

https://github.com/dosco/graphjin · scanned 2026-06-17 01:59 UTC (1 month, 1 week ago)

73 raw signals (0 security + 73 graph)

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

Complete repo analysis

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

JSON
Combined
66.5
/100
Security checks
67
0 findings
System graph
67
100.0% cov · 48 findings
Critical
4
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 4 High 3 Medium 11 Low 29 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 48 Crowd 0 Layer: Frontend 3 Security 9 Cicd 5 Quality 31
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 Repository scanned at 66.5/100 with 100.0% coverage. It contains 1269 nodes across 17 cross-layer flows, written primarily in mixed languages. Engine surfaced 73 findings — concentrated in quality (33), cicd (23), security (14). Risk profile is high: 9 critical, 3 high, 19 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 44 of 48 actionable findings. 73 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.

critical System graph security Secrets conf 1.00 5 occurrences Possible secret in cmd/cmd_demo.go
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 520, 577, 648, 761, 844
cmd/cmd_demo.go:520, 577, 648, 761, 844 (5 hits)
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in serv/mcp_discover.go
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 1111, 1127
serv/mcp_discover.go:1111, 1127 (2 hits)
high System graph security security conf 1.00 Insecure pattern 'eval_used' in core/role_match.go:16
Found a known-risky pattern (eval_used). Review and replace if possible.
core/role_match.go:16 Eval used
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: serv/web/.env
`serv/web/.env` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.
serv/web/.env ConfigEnv fileRuntime env
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: claude-plugins/graphjin-mcp/.mcp.json
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.
claude-plugins/graphjin-mcp/.mcp.json VerificationMcp config
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: skills/add-graphjin-database/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.
skills/add-graphjin-database/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 lockfile. 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
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph quality Integrity conf 1.00 3 occurrences Frontend route `/schema` has no Link/navigate to it — serv/web/src/App.jsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
3 occurrences
repo-level (3 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 7 occurrences GitHub Action is tag-pinned rather than SHA-pinned
crazy-max/ghaction-import-gpg@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 7 locations
.github/workflows/auto-release.yml:233, 240, 247 (3 hits)
.github/workflows/codeql-analysis.yml:18, 26, 40 (3 hits)
.github/workflows/deploy-website.yml:36
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/deploy-website.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in serv/http.go:494
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
serv/http.go:494 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in website/static/js/site.js:178
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
website/static/js/site.js:178 Direct innerhtml assignment
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 121 placeholder/mock markers across 46 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 7 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 13 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
4 files, 13 locations
.github/workflows/deploy-website.yml:26, 29, 42, 57, 71 (5 hits)
.github/workflows/auto-release.yml:22, 29, 133, 139 (4 hits)
.github/workflows/build.yml:21, 24, 29 (3 hits)
.github/workflows/codeql-analysis.yml:14
CI/CD securitySupply chainGithub actions
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: wasm/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
wasm/package.json LockfileReproducibilityGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
wasm/package.json CI/CD securitySupply chainNpm
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — benchmark/subs.js:50
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — wasm/js/wasm_exec.js:22
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: core/api.go (2999 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/config.go (1876 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/internal/catalog/build.go (1637 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/internal/dialect/mariadb.go (2681 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/internal/dialect/mongodb.go (4383 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/internal/dialect/mssql.go (3824 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/internal/introspection/tables.go (1746 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/schema_ddl.go (1878 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/schema_diff_test.go (2158 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: serv/control_plane_graphql.go (1350 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: serv/control_plane_graphql_test.go (2548 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: serv/mcp_catalog.go (1217 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: serv/mcp_config.go (3686 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: serv/mcp_schema.go (1667 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: serv/mcp_test.go (2092 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: serv/security_report.go (2260 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/hostedemu/snowflake/internal/sfparser/snowflake_lexer.go (8776 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/hostedemu/snowflake/internal/sfparser/snowflakeparser_base_listener.go (3451 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/hostedemu/snowflake/internal/sfparser/snowflakeparser_base_visitor.go (2172 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/hostedemu/snowflake/internal/sfparser/snowflakeparser_listener.go (3255 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/hostedemu/snowflake/internal/sfparser/snowflakeparser_visitor.go (1632 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/query_test.go (2623 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/b85d534a-9dfa-4cc8-a0a9-4a5f61f0b33f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/b85d534a-9dfa-4cc8-a0a9-4a5f61f0b33f/

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.