digitalv3rtice/confirmacao

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.

Scan timing: clone 2.8s · analysis 0.08s · 5.7 MB · GitHub API rate-limit (preflight)

https://github.com/digitalv3rtice/confirmacao.git · scanned 2026-05-27 21:30 UTC (1 week, 1 day ago) · 10 languages

22 findings (10 legacy + 12 scanner) 3rd percentile · Javascript · tiny (<2K LoC) Scanner says 80 (lower by 39)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 1 day ago · v2 · 16 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	30.0	0.15	4.50
`security_score`	97.0	0.25	24.25
`testing_score`	0.0	0.20	0.00
`documentation_score`	9.0	0.15	1.35
`practices_score`	30.0	0.15	4.50
`code_quality`	70.0	0.10	7.00
Overall		1.00	41.6

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 7 Low 4 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 10 9-layer 6 Crowd 0 Layer: Quality 11 Security 2 Api 1 Frontend 1 Cicd 1

Exclude dismissed / FP Exclude test files

Scan summary Repository scanned at 80.5/100 with 66.7% coverage. It contains 13 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 6 findings — concentrated in quality (2), api (1), frontend (1). Risk profile is low: 0 critical, 0 high, 4 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 12 of 16 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high Legacy security secret conf 1.00 [SEC061] JWT in source: Three-part JWT (likely signed token). Even if expired, may leak structure or claims. Ported from gitleaks jwt (MIT).

If the JWT is live, invalidate by rotating the signing key. Move tokens out of source.

script.js:6 secretlegacy

medium Legacy quality practices conf 1.00 [CFG006] Missing .gitignore: No .gitignore file. Risk of committing secrets and build artifacts.

Add a .gitignore appropriate for your language/framework.

practiceslegacy

medium Legacy quality quality conf 0.70 Public web app has no Content Security Policy

A Content Security Policy reduces the blast radius of injected scripts if the app is ever served through preview, static hosting, or a web container outside its normal sandbox.

index.html qualitylegacy

medium Legacy quality quality conf 0.78 Public web service has no security.txt

security.txt gives researchers and customers a safe disclosure channel. Public web apps and APIs should publish it under /.well-known/security.txt.

.well-known/security.txt qualitylegacy

medium 9-layer quality integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — script.js:13

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

integrityfragile-runtimerobustness

medium 9-layer security coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). Either auth lives in custom code, in a separate service, or is missing.

coverageauth

medium 9-layer cicd coverage 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.

coverage

medium 9-layer quality tests conf 1.00 Very low test-to-source ratio

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

testscoverage

low Legacy quality documentation No LICENSE file

Add a LICENSE file to your repository. Use choosealicense.com to pick the right license (MIT for permissive, Apache 2.0 for patent protection, GPL for copyleft).

documentationlegacy

low Legacy quality quality conf 0.50 Public web app has no humans.txt

humans.txt is optional, but it gives operators and reviewers a simple place to find ownership, contact, and important public documentation links.

humans.txt qualitylegacy

low Legacy quality quality conf 0.74 Public web app has no robots.txt

Public websites should publish a robots.txt file so crawlers and AI agents can discover crawl rules and sitemap locations without guessing.

robots.txt qualitylegacy

low Legacy quality quality conf 0.72 Public web app has no sitemap

A sitemap gives search engines, docs crawlers, and AI agents a structured list of public pages. Without one, important docs and product pages are easy to miss.

sitemap.xml qualitylegacy

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/65cb4b32-049b-4e90-bf2c-b965fe8b20f3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/65cb4b32-049b-4e90-bf2c-b965fe8b20f3/

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.