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.

lisalepardeany-coder/maowcore

https://github.com/lisalepardeany-coder/maowcore · scanned 2026-06-16 04:31 UTC (2 months ago)

14 raw signals (0 security + 14 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months ago · v1 · 13 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

77.8% cov · 13 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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

Showing 11 of 13 actionable findings. 14 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 cicd CI/CD security conf 1.00 No CI/CD pipelines detected

No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.

CI/CD securityCoverage

medium System graph network Security conf 1.00 Privileged port 1000 in use

Port 1000 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

docker-compose.yml Ports

low System graph quality Integrity conf 1.00 5 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `AUTO_DEPLOY_COMMANDS`, `COMMAND_PREFIX`, `FFMPEG_PATH`, `YTDLP_DIR`, `YTDLP_FILENAME`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

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

Multiple low-cost hardening controls are missing together: ci, lockfile. 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 quality Debug conf 1.00 Debug logging residue appears in source files

Found 12 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 hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:22-bookworm-slim

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

lines 18, 44

Dockerfile:18, 44 (2 hits)

containersPinned dependencies

low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

package.json LockfileReproducibilityGenerated repo pattern

low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts

preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.

package.json CI/CD securitySupply chainNpm

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy-commands.js:29

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 — index.js:52

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: index.js (1226 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/511effda-be1e-4953-9ad9-031964be0d3b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/511effda-be1e-4953-9ad9-031964be0d3b/

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.