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.

bobsilverstein/calorie-counter

https://github.com/bobsilverstein/calorie-counter · scanned 2026-06-17 01:41 UTC (1 month, 1 week ago)

13 raw signals (0 security + 13 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -12.3 (diff) · 11 actionable findings from 1 signal source. 2 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

66.7% cov · 11 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 0 Medium 7 Low 3 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 11 Crowd 0 Layer: Frontend 1 Security 5 Cicd 1 Quality 4

Exclude dismissed / FP Exclude test files

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 64.4/100 with 66.7% coverage. It contains 96 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 13 findings — concentrated in security (5), quality (4), cicd (3). Risk profile is high: 1 critical, 0 high, 9 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 11 of 11 actionable findings. 13 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 System graph security Secrets conf 1.00 Possible secret in public/firebase-config.js

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

public/firebase-config.js:2

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 cicd CI/CD security conf 1.00 3 occurrences 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.

3 files, 3 locations

.github/workflows/deploy.yml

.github/workflows/firebase-rules.yml

.github/workflows/preview.yml

CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Archive/v126 2 app.js:107

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

Archive/v126 2 app.js:107 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Archive/v126 3 app.js:141

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

Archive/v126 3 app.js:141 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Archive/v126 4 app.js:117

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

Archive/v126 4 app.js:117 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/app.js:285

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

public/app.js:285 Direct innerhtml assignment

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 5 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — public/app.js:660

A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label

Fq button no label

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

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/6c573b98-8d9e-49c7-971a-e0492bb663f9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6c573b98-8d9e-49c7-971a-e0492bb663f9/

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.