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

sebastienros/jint

https://github.com/sebastienros/jint · scanned 2026-06-16 00:06 UTC (2 months, 2 weeks ago)

75 raw signals (0 security + 75 graph)

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

Complete repo analysis

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

JSON
Combined
52.2
/100
Security checks
52
0 findings
System graph
52
88.9% cov · 67 findings
Critical
0
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 0 High 12 Medium 13 Low 22 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 67 Crowd 0 Layer: Frontend 15 Security 22 Cicd 1 Quality 29
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 52.2/100 with 88.9% coverage. It contains 3166 nodes across 1 cross-layer flows, written primarily in mixed languages. Engine surfaced 75 findings — concentrated in quality (29), security (22), frontend (15). Risk profile is high: 0 critical, 12 high, 13 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 30 of 67 actionable findings. 75 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 security security conf 1.00 Insecure pattern 'new_function_used' in Jint.Benchmark/Scripts/dromaeo-core-eval-modern.js:21
Found a known-risky pattern (new_function_used). Review and replace if possible.
Jint.Benchmark/Scripts/dromaeo-core-eval-modern.js:21 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in Jint.Benchmark/Scripts/dromaeo-core-eval.js:24
Found a known-risky pattern (new_function_used). Review and replace if possible.
Jint.Benchmark/Scripts/dromaeo-core-eval.js:24 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in Jint.Benchmark/Scripts/linq-js.js:1
Found a known-risky pattern (new_function_used). Review and replace if possible.
Jint.Benchmark/Scripts/linq-js.js:1 New function used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — Jint.Tests/Parser/Scripts/angular.js:7378
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 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 quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 100 placeholder/mock markers across 26 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Maintenance conf 1.00 32 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 52 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 9 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-dotnet@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 9 locations
.github/workflows/build.yml:22, 27, 30 (3 hits)
.github/workflows/pr.yml:36, 41, 44 (3 hits)
.github/workflows/release.yml:19, 24, 27 (3 hits)
CI/CD securitySupply chainGithub actions
low System graph security security conf 1.00 Insecure pattern 'document_write' in Jint.Benchmark/Scripts/linq-js.js:1
Found a known-risky pattern (document_write). Review and replace if possible.
Jint.Benchmark/Scripts/linq-js.js:1 Document write
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
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 — Jint.Benchmark/Scripts/linq-js.js:1
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 — Jint.Tests/Parser/Scripts/angular.js:5009
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 — Jint.Tests/Parser/Scripts/JSXTransformer.js:482
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 — Jint.Tests/Runtime/Scripts/prism.js:692
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: Jint.Benchmark/Scripts/template-rendering/lib/handlebars.js (5209 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Jint.Tests.CommonScripts/Scripts/regexp-dna.js (1721 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Jint.Tests/Parser/Scripts/angular.js (20368 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Jint.Tests/Parser/Scripts/backbone.js (1580 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Jint.Tests/Parser/Scripts/handlebars.js (3079 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Jint.Tests/Parser/Scripts/jQuery.js (9597 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Jint.Tests/Parser/Scripts/JSXTransformer.js (12573 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Jint.Tests/Parser/Scripts/mootools.js (6456 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Jint.Tests/Runtime/Scripts/handlebars.js (3085 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Jint.Tests/Runtime/Scripts/moment.js (5685 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Jint.Tests/Runtime/Scripts/prism.js (1665 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/928cd66c-52b0-4190-865b-c9476cff36b4/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/928cd66c-52b0-4190-865b-c9476cff36b4/

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.