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.

skofic/metadata-store-interface

https://github.com/skofic/metadata-store-interface · scanned 2026-06-16 00:14 UTC (2 months, 2 weeks ago)

26 raw signals (0 security + 26 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 26 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 · 26 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 7 Low 3 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 26 Crowd 0 Layer: Security 5 Cicd 1 Quality 19 Api 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 94.0/100 with 66.7% coverage. It contains 182 nodes across 3 cross-layer flows, written primarily in mixed languages. Engine surfaced 26 findings — concentrated in quality (19), security (5), cicd (1). Risk profile is low: 0 critical, 0 high, 7 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 10 of 26 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in src/components/LatexSpan.vue:2

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

src/components/LatexSpan.vue:2 Vue v html

medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in src/components/ObjectCard.vue:75

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

src/components/ObjectCard.vue:75 Vue v html

medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in src/components/TermCard.vue:77

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

src/components/TermCard.vue:77 Vue v html

medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in src/components/TextValue.vue:9

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

src/components/TextValue.vue:9 Vue v html

medium System graph security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

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 quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 25 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: 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 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 api Wiring conf 1.00 Unused endpoint: POST /term/bulk

`src/stores/dictionary.js` declares `POST /term/bulk` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

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/778badbe-185c-4ba6-94f0-b8127ecfed5b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/778badbe-185c-4ba6-94f0-b8127ecfed5b/

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.