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

carlos7ags/folio

https://github.com/carlos7ags/folio · scanned 2026-07-27 20:35 UTC (19 hours, 41 minutes ago)

35 raw signals (0 security + 35 graph)

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

Complete repo analysis

Last scanned 19 hours, 42 minutes ago · v1 · 34 actionable findings from 1 signal source. 1 repeated signal grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
49.6
/100
Security checks
50
0 findings
System graph
50
50.0% cov · 34 findings
Critical
0
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 0 High 0 Medium 27 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 34 Crowd 0 Layer: Security 22 Cicd 2 Quality 10
Scan summary Repository scanned at 49.6/100 with 50.0% coverage. It contains 708 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 35 findings — concentrated in security (22), quality (10), cicd (3). Risk profile is low: 0 critical, 0 high, 28 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 31 of 34 actionable findings. 35 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.

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 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 Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
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 cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-go@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 2 locations
.github/workflows/ci.yml:16
.github/workflows/release.yml:47
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/release.yml CI/CD securitySupply chainGithub actions
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 181 placeholder/mock markers across 53 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 security Secrets conf 0.58 Possible secret in document/encryption.go
Detected 1 occurrence(s) matching password_literal. Rotate real credentials and move them to a secret manager.
document/encryption.go:33 Password literal
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
medium System graph security Semgrep conf 0.70 use of md5 — core/decrypt.go:168
Detected MD5 hash algorithm which is considered insecure. MD5 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. Rule: go.lang.security.audit.crypto.use_of_weak_crypto.use-of-md5 Severity: WARNING OWASP: A03:2017 - Sensitive Data Expo…
core/decrypt.go:168 SecurityGo
medium System graph security Semgrep conf 0.70 use of md5 — core/encrypt.go:267
Detected MD5 hash algorithm which is considered insecure. MD5 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. Rule: go.lang.security.audit.crypto.use_of_weak_crypto.use-of-md5 Severity: WARNING OWASP: A03:2017 - Sensitive Data Expo…
core/encrypt.go:267 SecurityGo
medium System graph security Semgrep conf 0.70 use of md5 — document/writer_xref_stream.go:403
Detected MD5 hash algorithm which is considered insecure. MD5 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. Rule: go.lang.security.audit.crypto.use_of_weak_crypto.use-of-md5 Severity: WARNING OWASP: A03:2017 - Sensitive Data Expo…
document/writer_xref_stream.go:403 SecurityGo
medium System graph security Semgrep conf 0.70 use of rc4 — core/encrypt.go:565
Detected RC4 cipher algorithm which is insecure. The algorithm has many known vulnerabilities. Use AES instead. Rule: go.lang.security.audit.crypto.use_of_weak_crypto.use-of-rc4 Severity: WARNING OWASP: A03:2017 - Sensitive Data Exposure, A02:2021 - Cryptographic Failures, A04:2025 - Cryptographic…
core/encrypt.go:565 SecurityGo
medium System graph security Semgrep conf 0.70 use of sha1 — sign/dss.go:174
Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. Rule: go.lang.security.audit.crypto.use_of_weak_crypto.use-of-sha1 Severity: WARNING OWASP: A03:2017 - Sensitive Data E…
sign/dss.go:174 SecurityGo
medium System graph security Semgrep conf 0.55 use of unsafe block — export/cabi.go:173
Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'…
export/cabi.go:173 SecurityGo
medium System graph security Semgrep conf 0.55 use of unsafe block — export/cabi_buffer.go:33
Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'…
export/cabi_buffer.go:33 SecurityGo
medium System graph security Semgrep conf 0.55 use of unsafe block — export/cabi_columns.go:45
Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'…
export/cabi_columns.go:45 SecurityGo
medium System graph security Semgrep conf 0.55 use of unsafe block — export/cabi_forms.go:70
Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'…
export/cabi_forms.go:70 SecurityGo
medium System graph security Semgrep conf 0.55 use of unsafe block — export/cabi_forms_ext.go:57
Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'…
export/cabi_forms_ext.go:57 SecurityGo
medium System graph security Semgrep conf 0.55 use of unsafe block — export/cabi_grid.go:55
Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'…
export/cabi_grid.go:55 SecurityGo
medium System graph security Semgrep conf 0.55 use of unsafe block — export/cabi_merge.go:30
Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'…
export/cabi_merge.go:30 SecurityGo
medium System graph security Semgrep conf 0.55 use of unsafe block — export/cabi_page_ext.go:102
Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'…
export/cabi_page_ext.go:102 SecurityGo
medium System graph security Semgrep conf 0.55 use of unsafe block — export/cabi_redact.go:34
Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'…
export/cabi_redact.go:34 SecurityGo
medium System graph security Semgrep conf 0.55 use of unsafe block — export/cabi_tab.go:31
Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'…
export/cabi_tab.go:31 SecurityGo
medium System graph security Semgrep conf 0.55 use of unsafe block — export/cabi_table.go:36
Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'…
export/cabi_table.go:36 SecurityGo
medium System graph security Semgrep conf 0.55 use of unsafe block — export/cabi_v062.go:230
Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'…
export/cabi_v062.go:230 SecurityGo
low System graph quality Complexity conf 1.00 Very large file: font/gpos_test.go (1781 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: font/metrics_data.go (6634 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: html/converter_test.go (9481 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: html/features_test.go (2840 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: layout/table.go (1721 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/c31098f4-744b-4782-b074-b7f4c6eb1d9e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c31098f4-744b-4782-b074-b7f4c6eb1d9e/

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.