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

Real-Fruit-Snacks/notes

https://github.com/Real-Fruit-Snacks/notes · scanned 2026-06-15 23:48 UTC (2 months, 3 weeks ago)

30 raw signals (0 security + 30 graph)

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

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 30 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

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

Showing 21 of 30 actionable findings. 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 security conf 1.00 Insecure pattern 'private_key_in_repo' in assets/tools/certs.js:424
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
assets/tools/certs.js:424 Private key in repo
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — assets/tools/ports.js:98
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
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 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.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in assets/localgraph.js:48
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
assets/localgraph.js:48 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in assets/previews.js:25
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
assets/previews.js:25 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in assets/search.js:25
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
assets/search.js:25 Direct innerhtml assignment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 8 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 GitHub Action is tag-pinned rather than SHA-pinned
actions/deploy-pages@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/deploy.yml:58 CI/CD securitySupply chainGithub actions
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 quality Integrity conf 1.00 Old/deprecated-named symbol `test_vendor_katex_mermaid_absent_when_unused` in tests/test_fixes.py:165
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: callout_core
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
obsidian_site/rules/callout.py:40
low System graph software Dead code conf 1.00 Possibly dead Python function: callout_plugin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
obsidian_site/rules/callout.py:89
low System graph software Dead code conf 1.00 Possibly dead Python function: hashtag_plugin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
obsidian_site/rules/hashtag.py:71
low System graph software Dead code conf 1.00 Possibly dead Python function: hashtags_core
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
obsidian_site/rules/hashtag.py:57
low System graph software Dead code conf 1.00 Possibly dead Python function: heading_plugin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
obsidian_site/rules/heading.py:62
low System graph software Dead code conf 1.00 Possibly dead Python function: unwrap_embeds_core
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
obsidian_site/rules/transclusion.py:25
low System graph software Dead code conf 1.00 Possibly dead Python function: unwrap_embeds_plugin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
obsidian_site/rules/transclusion.py:39
low System graph software Dead code conf 1.00 Possibly dead Python function: wikilink_inline
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
obsidian_site/rules/wikilink.py:31
low System graph software Dead code conf 1.00 Possibly dead Python function: wikilink_plugin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
obsidian_site/rules/wikilink.py:74
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
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/07c09b44-90af-403b-b15d-38b002af96a7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/07c09b44-90af-403b-b15d-38b002af96a7/

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.