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

yuyanishimura0312/miratuku-news-v2

https://github.com/yuyanishimura0312/miratuku-news-v2 · scanned 2026-06-16 01:11 UTC (2 months, 1 week ago)

155 raw signals (0 security + 155 graph)

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

Complete repo analysis

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

JSON
Combined
62.3
/100
Security checks
62
0 findings
System graph
62
88.9% cov · 124 findings
Critical
3
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 3 High 0 Medium 87 Low 33 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 124 Crowd 0 Layer: Software 16 Frontend 1 Security 59 Cicd 2 Quality 46

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in js/shared/firebase-config.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in js/shared/firebase-config.js:3; move to env var / secrets manager.
js/shared/firebase-config.js:3
#2
Possible secret in js/shared/i18n.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in js/shared/i18n.js:134; move to env var / secrets manager.
js/shared/i18n.js:134
#3
Possible secret in admin/index.html
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in admin/index.html:804; move to env var / secrets manager.
admin/index.html:804
#4
Insecure pattern 'direct_innerhtml_assignment' in integrated-monetization-textbook.html:3835
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
integrated-monetization-textbook.html:3835
#5
Insecure pattern 'direct_innerhtml_assignment' in db-planner.html:380
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
db-planner.html:380
#6
Insecure pattern 'direct_innerhtml_assignment' in integrated.html:296
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
integrated.html:296
#7
Insecure pattern 'direct_innerhtml_assignment' in answer.html:1523
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
answer.html:1523
#8
Insecure pattern 'direct_innerhtml_assignment' in databases.html:1329
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
databases.html:1329
#9
Insecure pattern 'direct_innerhtml_assignment' in forum/esse-sense-co-creation-2026-06-03-k9m4x/edit/index.html:308
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
forum/esse-sense-co-creation-2026-06-03-k9m4x/edit/index.html:308
#10
Insecure pattern 'direct_innerhtml_assignment' in js/foresight.js:114
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
js/foresight.js:114

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/48f53bf2-f021-4175-a2e9-3e6190f15cb5/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/48f53bf2-f021-4175-a2e9-3e6190f15cb5/

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.