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.
Sign up free Scan another repo

Zillatron27/APXM

https://github.com/Zillatron27/APXM · scanned 2026-06-16 01:12 UTC (2 months, 1 week ago)

38 raw signals (12 security + 26 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 35 actionable findings from 2 signal sources. 78 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
99.1
/100
Security checks
99
9 findings
System graph
99
66.7% cov · 26 findings
Critical
3
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 3 High 4 Medium 5 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 26 Crowd 0 Layer: Quality 19 Cicd 3 Security 2 Frontend 11
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 99.1/100 with 66.7% coverage. It contains 511 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 26 findings — concentrated in quality (12), frontend (11), cicd (2). Risk profile is low: 0 critical, 0 high, 3 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 19 of 35 actionable findings. 113 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.

critical Security checks cicd CI/CD security conf 0.86 Foundry mined claimed resolved with failing ci: Zillatron27/APXM
Graph query export: Claimed resolved with failing CI Query id: claimed_resolved_with_failing_ci Query type: motif_query Intent: Hard negatives where CI/failure evidence contradicts a resolution claim. Motif: claimed_resolved_with_failing_ci Training usage: hard_negative Graph gold label: contradict…
CI/CD securityCI/CD
critical Security checks quality Practices conf 0.82 2 occurrences Foundry mined mock as real or placeholder: Zillatron27/APXM
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
2 occurrences
repo-level (2 hits)
critical Security checks security auth conf 0.78 2 occurrences Foundry mined security auth guardrail gaps: Zillatron27/APXM
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
2 occurrences
repo-level (2 hits)
high Security checks quality Practices conf 0.84 11 occurrences Foundry mined bad chains: Zillatron27/APXM
Comment chain pattern product: bad_chains Repo: Zillatron27/APXM Thread: Zillatron27/APXM#59 Outcome: claimed_resolved_with_failing_ci_signal Thread label: thread_has_human_issue_and_fix_context Source graph label: source_artifact_without_verification_graph Reasons: source_graph_has_real_artifacts,…
11 occurrences
repo-level (11 hits)
high Security checks quality Practices conf 0.80 Foundry mined docs only runtime fix: Zillatron27/APXM
Graph query export: Docs-only response to runtime or integration issue Query id: docs_only_runtime_fix Query type: motif_query Intent: Assumption-check examples where docs or claims are not enough proof. Motif: docs_only_runtime_fix Training usage: assumption_check Graph gold label: supported_by_ve…
high Security checks quality Quality conf 0.76 3 occurrences Foundry mined schema ui api mismatch: Zillatron27/APXM
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: supported_by_verification_signal Repo…
3 occurrences
repo-level (3 hits)
high Security checks quality Testing conf 0.78 20 occurrences Foundry mined test ci gap after feedback: Zillatron27/APXM
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: contradicted_by_ci_or_f…
20 occurrences
repo-level (20 hits)
medium Security checks quality Practices conf 0.62 32 occurrences Foundry mined assumption checks: Zillatron27/APXM
Comment chain pattern product: assumption_checks Repo: Zillatron27/APXM Thread: Zillatron27/APXM#9 Outcome: ambiguous_needs_more_evidence Thread label: thread_needs_classification Source graph label: source_artifact_without_verification_graph Reasons: source_graph_has_real_artifacts, link_quality_u…
32 occurrences
repo-level (32 hits)
medium Security checks quality Practices conf 0.70 15 occurrences Foundry mined unresolved feedback: Zillatron27/APXM
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
15 occurrences
repo-level (15 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — entrypoints/content.tsx:182
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 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
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 8 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 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 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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — lib/buffer-refresh/dom-helpers.ts:228
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 — lib/debug/logger.ts:23
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 — lib/diagnostics.ts:75
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: core/__tests__/burn.test.ts (1667 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/73d38b60-886f-49a5-9b7d-47985e0555a0/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/73d38b60-886f-49a5-9b7d-47985e0555a0/

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.