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

Sigil-Core/sigil-open-framework

https://github.com/Sigil-Core/sigil-open-framework · scanned 2026-06-16 00:12 UTC (2 months, 2 weeks ago)

34 raw signals (20 security + 14 graph)

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

Complete repo analysis

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

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

Showing 20 of 22 actionable findings. 43 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 quality Practices conf 0.82 Foundry mined mock as real or placeholder: Sigil-Core/sigil-open-framework
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…
critical Security checks security auth conf 0.78 6 occurrences Foundry mined security auth guardrail gaps: Sigil-Core/sigil-open-framework
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…
6 occurrences
repo-level (6 hits)
high Security checks quality Practices conf 0.84 2 occurrences Foundry mined bad chains: Sigil-Core/sigil-open-framework
Comment chain pattern product: bad_chains Repo: Sigil-Core/sigil-open-framework Thread: Sigil-Core/sigil-open-framework#9 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_gra…
2 occurrences
repo-level (2 hits)
high Security checks quality Practices conf 0.80 4 occurrences Foundry mined docs only runtime fix: Sigil-Core/sigil-open-framework
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: weak_supervisio…
4 occurrences
repo-level (4 hits)
high Security checks quality Quality conf 0.76 Foundry mined schema ui api mismatch: Sigil-Core/sigil-open-framework
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…
medium Security checks quality Practices conf 0.62 6 occurrences Foundry mined assumption checks: Sigil-Core/sigil-open-framework
Comment chain pattern product: assumption_checks Repo: Sigil-Core/sigil-open-framework Thread: Sigil-Core/sigil-open-framework#8 Outcome: ambiguous_needs_more_evidence Thread label: thread_has_human_issue_and_fix_context Source graph label: source_artifact_without_verification_graph Reasons: source…
6 occurrences
repo-level (6 hits)
medium Security checks quality maintenance conf 0.70 8 occurrences Foundry mined blueprint gap alignment: Sigil-Core/sigil-open-framework
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
8 occurrences
repo-level (8 hits)
medium Security checks quality Practices conf 0.70 Foundry mined unresolved feedback: Sigil-Core/sigil-open-framework
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: assu…
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — demo/demo.ts:56
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 quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — developer-toolkit/sigil_authorizer.py:62
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
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 4 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 24 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 quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: demo/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
demo/package.json LockfileReproducibilityGenerated 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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — demo/demo.ts:48
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 — developer-toolkit/mock_server.js:11
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 api Wiring conf 1.00 Unused endpoint: POST /v1/authorize
`developer-toolkit/mock_server.js` declares `POST /v1/authorize` 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/585c967a-6222-4517-8523-81e151e252b9/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/585c967a-6222-4517-8523-81e151e252b9/

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.