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.

zuzuscript/stdlib

https://github.com/zuzuscript/stdlib · scanned 2026-06-16 01:14 UTC (2 months, 1 week ago)

7 raw signals (3 security + 4 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

66.7% cov · 4 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

Showing 6 of 7 actionable findings. 9 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 Security checks quality Practices conf 0.84 Foundry mined bad chains: zuzuscript/stdlib

Comment chain pattern product: bad_chains Repo: zuzuscript/stdlib Thread: zuzuscript/stdlib#4 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_artifact_without_verification_graph Reasons: source_graph_has_real_artifacts, repo_…

medium Security checks quality Practices conf 0.62 3 occurrences Foundry mined assumption checks: zuzuscript/stdlib

Comment chain pattern product: assumption_checks Repo: zuzuscript/stdlib Thread: zuzuscript/stdlib#3 Outcome: ambiguous_needs_more_evidence Thread label: thread_needs_classification Source graph label: source_artifact_without_verification_graph Reasons: source_graph_has_real_artifacts, repo_has_iso…

3 occurrences

repo-level (3 hits)

medium Security checks quality Practices conf 0.70 Foundry mined unresolved feedback: zuzuscript/stdlib

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…

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 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/0be1aa33-ca13-4ece-9060-348ac15114e5/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0be1aa33-ca13-4ece-9060-348ac15114e5/

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.