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

theRoadz/FarmOS

https://github.com/theRoadz/FarmOS · scanned 2026-06-16 00:35 UTC (2 months, 2 weeks ago)

157 raw signals (0 security + 157 graph)

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

Complete repo analysis

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

JSON
Combined
59.4
/100
Security checks
59
0 findings
System graph
59
88.9% cov · 133 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 2 Medium 4 Low 17 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 133 Crowd 0 Layer: Frontend 6 Network 1 Security 5 Cicd 3 Quality 118
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 59.4/100 with 88.9% coverage. It contains 1024 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 157 findings — concentrated in quality (118), cicd (27), frontend (6). Risk profile is high: 3 critical, 2 high, 15 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 26 of 133 actionable findings. 157 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 apps/farmos/web/firebase-messaging-sw.js
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
apps/farmos/web/firebase-messaging-sw.js:39
critical System graph security Secrets conf 1.00 Possible secret in apps/farmos/web/firebase-messaging-sw_development.js
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
apps/farmos/web/firebase-messaging-sw_development.js:39
critical System graph security Secrets conf 1.00 Possible secret in apps/farmos/web/firebase-messaging-sw_staging.js
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
apps/farmos/web/firebase-messaging-sw_staging.js:36
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: functions/.env.farmos-devs
`functions/.env.farmos-devs` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.
functions/.env.farmos-devs ConfigEnv fileRuntime env
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: functions/.env.farmos-staging
`functions/.env.farmos-staging` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.
functions/.env.farmos-staging ConfigEnv fileRuntime env
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 12 occurrences GitHub Action is tag-pinned rather than SHA-pinned
subosito/flutter-action@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
7 files, 12 locations
.github/workflows/offline-soak.yml:85, 127, 210, 284 (4 hits)
apps/farmos/.github/workflows/main.yaml:17, 20, 26 (3 hits)
.github/workflows/golden-rebaseline.yml:42
.github/workflows/pr.yml:59
.github/workflows/prod-release.yml:57
.github/workflows/staging-deploy.yml:41
apps/farmos/.github/workflows/license_check.yaml:23
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/golden-rebaseline.yml CI/CD securitySupply chainGithub actions
medium System graph network Security conf 1.00 Privileged port 19 in use
Port 19 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
_bmad-output/implementation-artifacts/sprint-status.yaml Ports
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 14 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
5 files, 14 locations
.github/workflows/offline-soak.yml:69, 74, 79, 117, 250, 279 (6 hits)
.github/workflows/pr.yml:47, 50, 105 (3 hits)
.github/workflows/prod-release.yml:38, 48 (2 hits)
.github/workflows/staging-deploy.yml:29, 32 (2 hits)
.github/workflows/golden-rebaseline.yml:36
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `batch_alpha_001_v2` in rules-tests/livestock_batches.test.ts:804
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 quality Integrity conf 1.00 Old/deprecated-named symbol `entry_e_v2` in functions/test/triggers/onAmountDetailWrite.test.ts:280
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 quality Integrity conf 1.00 Old/deprecated-named symbol `event_alpha_001_v2` in rules-tests/livestock_events.test.ts:1112
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 quality Integrity conf 1.00 Old/deprecated-named symbol `farmOld` in functions/test/triggers/staleSaleNudge.test.ts:243
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 quality Integrity conf 1.00 Old/deprecated-named symbol `id_doc_v1` in rules-tests/storage_farm_docs.test.ts:47
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 quality Integrity conf 1.00 Old/deprecated-named symbol `ind_alpha_001_v2` in rules-tests/livestock_individuals.test.ts:652
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 quality Integrity conf 1.00 Old/deprecated-named symbol `lease_alpha_001_v2` in rules-tests/leases.test.ts:694
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 quality Integrity conf 1.00 Old/deprecated-named symbol `project_cloud_logging_canonical_filter_v2` in functions/src/callable/rejectPendingApproval.ts:14
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 quality Integrity conf 1.00 Old/deprecated-named symbol `tenant_alpha_001_v2` in rules-tests/tenants.test.ts:696
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 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
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — functions/src/scripts/backfill_user_memberships.ts:88
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — shared/scripts/backfill_member_display_names.ts:157
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — shared/scripts/seed_platform_config.ts:295
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Complexity conf 1.00 Very large file: rules-tests/leases.test.ts (2676 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: rules-tests/livestock_events.test.ts (2253 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/18d55a6b-e591-4248-9431-661c62a82cbd/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/18d55a6b-e591-4248-9431-661c62a82cbd/

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.