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.

bbyvfrd/squad_app

https://github.com/bbyvfrd/squad_app · scanned 2026-06-17 01:38 UTC (1 month, 2 weeks ago)

25 raw signals (0 security + 25 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 18 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 9 Low 3 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 18 Crowd 0 Layer: Hardware 1 Security 2 Cicd 2 Quality 13

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 65.4/100 with 88.9% coverage. It contains 381 nodes across 2 cross-layer flows, written primarily in mixed languages. Engine surfaced 25 findings — concentrated in quality (13), cicd (7), hardware (3). Risk profile is low: 0 critical, 0 high, 14 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 12 of 18 actionable findings. 25 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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — docs/context/design/ui_kits/squad_app/design-canvas.jsx:135

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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — docs/context/design/ui_kits/squad_app/image-slot.js:64

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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

CLAUDE.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: docs/context/design/SKILL.md

docs/context/design/SKILL.md VerificationSkill file

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 license. 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 cicd CI/CD security conf 1.00 6 occurrences GitHub Action is tag-pinned rather than SHA-pinned

gitleaks/gitleaks-action@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

lines 30, 101, 109, 129, 135, 144

.github/workflows/ci.yml:30, 101, 109, 129, 135, 144 (6 hits)

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/ci.yml CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/context/design/preview/a11y_contrast.html:71

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

docs/context/design/preview/a11y_contrast.html:71 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/context/design/ui_kits/squad_app/image-slot.js:237

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

docs/context/design/ui_kits/squad_app/image-slot.js:237 Direct innerhtml assignment

low System graph hardware Supply chain conf 1.00 3 occurrences Docker base image is tag-pinned but not digest-pinned: node:24-alpine

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

lines 2, 9, 24

Dockerfile:2, 9, 24 (3 hits)

containersPinned dependencies

low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence

The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.

Governance

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/9a6d0cd3-0751-43ce-bb1f-541d732b8328/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9a6d0cd3-0751-43ce-bb1f-541d732b8328/

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.