← Back to scan
File as GitHub Issue repo: digitalv3rtice/confirmacao

Push this scan report to digitalv3rtice/confirmacao

Click the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.

Embedded score card image

This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.

Repobility score card

Issue title

Public web app has no Content Security Policy

Curate findings to include

Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.

Top 5 (default)
Severity Rule Title File:line
HIGH SEC061 [SEC061] JWT in source: Three-part JWT (likely signed token). Even if expired, may leak s… script.js:6
HIGH CORE_NO_TESTS No test files found —
MED CFG006 [CFG006] Missing .gitignore: No .gitignore file. Risk of committing secrets and build art… —
MED WEB003 Public web service has no security.txt .well-known/security.txt
MED WEB015 Public web app has no Content Security Policy index.html
MED CORE_NO_CI No CI/CD configuration found —
LOW WEB001 Public web app has no robots.txt robots.txt
LOW WEB002 Public web app has no sitemap sitemap.xml
LOW WEB011 Public web app has no humans.txt humans.txt
LOW CORE_NO_LICENSE No LICENSE file —
Reset to top 5 10 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `digitalv3rtice/confirmacao`

**Score: 68/100 (D)**  ·  10 findings  ·  scanned 2026-05-27 21:30 UTC  ·  227 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 2 |
| MEDIUM | 4 |
| LOW | 4 |

📊 [Full filterable report](https://repobility.com/scan/65cb4b32-049b-4e90-bf2c-b965fe8b20f3/)  ·  ![scorecard](https://repobility.com/scan/65cb4b32-049b-4e90-bf2c-b965fe8b20f3/report.png?v=1779917420-s2)

### Top findings

1. **HIGH** `SEC061` — JWT in source
   `script.js:6` · A07:2021 Identification & Authentication Failures
2. **HIGH** `CORE_NO_TESTS` — No test files found
3. **MEDIUM** `CFG006` — Missing .gitignore
4. **MEDIUM** `WEB003` — Public web service has no security.txt
   `.well-known/security.txt`
5. **MEDIUM** `WEB015` — Public web app has no Content Security Policy
   `index.html`

---

**Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately.

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/65cb4b32-049b-4e90-bf2c-b965fe8b20f3/_
Premium account
This scan was submitted by a Enterprise-tier account. Premium accounts have full outreach control â Repobility doesn't pre-fill the 'file as GitHub issue' button for paid users. You can still file the issue manually using the markdown body above (Copy markdown), or contact us if you'd like batch-filing enabled for your account.
Megaproject â high spam risk
Could not determine 'digitalv3rtice/confirmacao' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
I read the warnings â override Cancel

The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.

For real security findings on big repos: use the project's SECURITY.md or private advisory flow instead of a public issue.