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.

yemfan/helmsmart

https://github.com/yemfan/helmsmart · scanned 2026-06-16 01:06 UTC (2 months, 1 week ago)

822 raw signals (210 security + 612 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 610 actionable findings from 2 signal sources. 288 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

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

#1
Possible secret in apps/leadsmartai/scripts/verify-app-review-demo-signin.mjs
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 apps/leadsmartai/scripts/verify-app-review-demo-signin.mjs:56; move to env var / secrets manager.
apps/leadsmartai/scripts/verify-app-review-demo-signin.mjs:56
#2
Possible secret in apps/leadsmartai/scripts/seed-app-review-demo-account.mjs
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 apps/leadsmartai/scripts/seed-app-review-demo-account.mjs:51; move to env var / secrets manager.
apps/leadsmartai/scripts/seed-app-review-demo-account.mjs:51
#3
Runtime dotenv file present in repo: apps/leadsmartai/.env.production
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in apps/leadsmartai/.env.production; move to env var / secrets manager.
apps/leadsmartai/.env.production
#4
Runtime dotenv file present in repo: apps/propertytoolsai/.env.production
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in apps/propertytoolsai/.env.production; move to env var / secrets manager.
apps/propertytoolsai/.env.production
#5
Insecure pattern 'exec_used' in docs/financial-services-pitch/README.md:77
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
docs/financial-services-pitch/README.md:77
#6
`dangerouslySetInnerHTML` used in a React component — apps/helmsmart-web/components/email-campaign-editor.tsx:253
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#7
`dangerouslySetInnerHTML` used in a React component — apps/leadsmartai/components/JsonLd.tsx:10
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#8
`dangerouslySetInnerHTML` used in a React component — apps/leadsmartai/components/dashboard/BrandingSettingsPanel.tsx:385
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#9
`dangerouslySetInnerHTML` used in a React component — apps/leadsmartai/components/dashboard/SendRecommendationsButton.tsx:328
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#10
`dangerouslySetInnerHTML` used in a React component — apps/leadsmartai/app/layout.tsx:190
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity

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/0a2c56cf-eb3f-4044-af75-2be6e174d755/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0a2c56cf-eb3f-4044-af75-2be6e174d755/

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.