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

JP401cmd/fin-first

https://github.com/JP401cmd/fin-first · scanned 2026-06-16 02:54 UTC (2 months, 1 week ago)

51 raw signals (24 security + 27 graph)

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

Complete repo analysis

Last scanned 2 months, 1 week ago · v2 · 35 actionable findings from 2 signal sources. 61 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
67.2
/100
Security checks
67
8 findings
System graph
67
88.9% cov · 27 findings
Critical
2
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 2 High 4 Medium 14 Low 11 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 27 Crowd 0 Layer: Quality 15 Security 9 Frontend 8 Hardware 1 Cicd 2
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 67.2/100 with 88.9% coverage. It contains 49 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 27 findings — concentrated in frontend (8), quality (8), security (8). Risk profile is low: 0 critical, 0 high, 12 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 31 of 35 actionable findings. 96 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 Security checks quality Practices conf 0.82 5 occurrences Foundry mined mock as real or placeholder: JP401cmd/fin-first
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
5 occurrences
repo-level (5 hits)
critical Security checks security auth conf 0.78 Foundry mined security auth guardrail gaps: JP401cmd/fin-first
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
high Security checks quality Practices conf 0.84 21 occurrences Foundry mined bad chains: JP401cmd/fin-first
Comment chain pattern product: bad_chains Repo: JP401cmd/fin-first Thread: JP401cmd/fin-first#9 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_…
21 occurrences
repo-level (21 hits)
high Security checks quality Practices conf 0.80 Foundry mined docs only runtime fix: JP401cmd/fin-first
Graph query export: Docs-only response to runtime or integration issue Query id: docs_only_runtime_fix Query type: motif_query Intent: Assumption-check examples where docs or claims are not enough proof. Motif: docs_only_runtime_fix Training usage: assumption_check Graph gold label: needs_more_evid…
high Security checks quality Quality conf 0.76 3 occurrences Foundry mined schema ui api mismatch: JP401cmd/fin-first
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: assumption_check Repo: JP401cmd/fin-f…
3 occurrences
repo-level (3 hits)
high Security checks quality Testing conf 0.78 2 occurrences Foundry mined test ci gap after feedback: JP401cmd/fin-first
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_verificati…
2 occurrences
repo-level (2 hits)
medium Security checks quality maintenance conf 0.70 15 occurrences Foundry mined blueprint gap alignment: JP401cmd/fin-first
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
15 occurrences
repo-level (15 hits)
medium Security checks quality Practices conf 0.70 21 occurrences Foundry mined unresolved feedback: JP401cmd/fin-first
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: assu…
21 occurrences
repo-level (21 hits)
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 license, ci, tests. 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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in trifinity-pitch.html:1333
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
trifinity-pitch.html:1333 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in trifinity-presentatie.html:2280
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
trifinity-presentatie.html:2280 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in trifinity-soa-architectuur.html:473
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
trifinity-soa-architectuur.html:473 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in devstral-cli.js:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
devstral-cli.js:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in kill-servers.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
kill-servers.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in start-server-4131.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
start-server-4131.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in start-server-f131.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
start-server-f131.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in start-server.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
start-server.js:1 Node child process
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
1 test file(s) for 13 source file(s) (ratio 0.08). Consider adding integration or unit tests for critical paths.
Coverage
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 63 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 quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated 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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — _update_claude.js:1
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 — check-port.js:6
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 — devstral-cli.js:29
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 — kill-servers.js:9
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 — start-server-4131.js:13
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 — start-server-f131.js:19
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 — start-server.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
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/d8615396-3733-4c01-b3c8-01a9fe952fe3/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d8615396-3733-4c01-b3c8-01a9fe952fe3/

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.