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.

xemantic/xemantic-typescript-compiler

https://github.com/xemantic/xemantic-typescript-compiler · scanned 2026-06-16 01:02 UTC (2 months, 1 week 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, 1 week ago · v1 · 10 actionable findings from 1 signal source. 4 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

55.6% cov · 10 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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

Showing 8 of 10 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.

high System graph cicd CI/CD security conf 1.00 5 occurrences GitHub Action tracks a moving branch

xemantic/.github/.github/workflows/build-gradle.yml@main can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

5 files, 5 locations

.github/workflows/build-main.yml:11

.github/workflows/build-pr.yml:9

.github/workflows/build-release.yml:20

.github/workflows/claude-code-review.yml:10

.github/workflows/claude-code.yml:16

CI/CD securitySupply chainGithub actions

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 tests. 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 quality Tests conf 1.00 CI is configured but no tests are detected

A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.

CI/CDConfig theaterRepo hardening

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

0 test file(s) for 6 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 45 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 software Dead code conf 1.00 Possibly dead Python function: irrelevant_bases

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/tsgo_relevance.py:177

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

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/e4825428-e27e-42df-8cd5-cf7bfac581b9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e4825428-e27e-42df-8cd5-cf7bfac581b9/

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.