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.

thematters/matters-web

https://github.com/thematters/matters-web · scanned 2026-06-16 04:40 UTC (1 month, 3 weeks ago)

6 raw signals (0 security + 6 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

66.7% cov · 6 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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

Showing 5 of 6 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 Secrets conf 1.00 Runtime dotenv file present in repo: .env.dev

`.env.dev` looks like a runtime dotenv file. It contains secret-looking assignments for NEXT_PUBLIC_SEGMENT_KEY, NEXT_PUBLIC_SENTRY_PUBLIC_KEY, NEXT_PUBLIC_ALCHEMY_KEY, NEXT_PUBLIC_CF_TURNSTILE_SITE_KEY. Move real values to a secret manager and keep only `.env.example` style templates in source con…

.env.dev ConfigEnv fileRuntime env

critical System graph security Secrets conf 1.00 Runtime dotenv file present in repo: .env.prod

`.env.prod` looks like a runtime dotenv file. It contains secret-looking assignments for NEXT_PUBLIC_SEGMENT_KEY, NEXT_PUBLIC_SENTRY_PUBLIC_KEY, NEXT_PUBLIC_STRIPE_PUBLIC_KEY, NEXT_PUBLIC_ALCHEMY_KEY, NEXT_PUBLIC_CF_TURNSTILE_SITE_KEY. Move real values to a secret manager and keep only `.env.exampl…

.env.prod ConfigEnv fileRuntime env

critical System graph security Secrets conf 1.00 Runtime dotenv file present in repo: .env.prod-next

`.env.prod-next` looks like a runtime dotenv file. It contains secret-looking assignments for NEXT_PUBLIC_SEGMENT_KEY, NEXT_PUBLIC_SENTRY_PUBLIC_KEY, NEXT_PUBLIC_STRIPE_PUBLIC_KEY, NEXT_PUBLIC_ALCHEMY_KEY, NEXT_PUBLIC_CF_TURNSTILE_SITE_KEY. Move real values to a secret manager and keep only `.env.e…

.env.prod-next ConfigEnv fileRuntime env

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

Multiple low-cost hardening controls are missing together: ci, 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 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

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/3637101f-6629-4f82-8c09-d42a1999479a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3637101f-6629-4f82-8c09-d42a1999479a/

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.