SasanLabs/VulnerableApp · audit

SasanLabs/VulnerableApp ↗ · 0c670ed · Aug 21, 2026, 11:15 PM

No deterministic issues foundNo problems found by this automatic checkNo issues found

Free scan · deterministic evidence onlyFree scan · found by automatic checks onlyFree scan · deterministic evidence only

The secret and dependency scanners surfaced nothing verdict-bearing in what they scanned. This is not a clean bill of health. These two scanners cover a sliver of production-readiness — the 14 dimensions that actually decide whether you ship are unaudited below. Run Audit for the verdict.

The checks for leaked passwords and known package bugs found nothing to flag. This does not mean your code is safe. These two checks cover only a small slice of what matters — the 14 areas that actually decide whether your code is ready to ship are not checked yet. Run Audit for the full verdict.

No deterministic issues found — not a clean bill of health. 14 dimensions remain unaudited. Run Audit for the verdict.

330 of 461 files scanned (71%). Nothing was cut short by a limit — the rest is mostly images, generated output, and other non-source content this audit doesn't read.

What this meansWhat this means for youWhat this means

Two scanners read 330 of 461 files: one for committed credentials, one for known vulnerabilities in your dependencies. Neither found anything. That is not a clean bill of health. These two checks cover a narrow slice of what decides whether software is ready to ship. All 14 dimensions — architecture, privacy, reliability, AI-generated-code risk and the rest — are unexamined here. Deep AI is the tier that issues a verdict. This scan does not.

Read it:

Worth knowing, not blocking

14 found · 7 files · 11 in tests

Test/example/doc credentials and devDependency or moderate/low CVEs. Surfaced as context — these never force the worst verdict.Passwords found in test, example or documentation files, and lower-severity security bugs in packages only used while building the project. Shown for context — these never cause the worst possible result.Context only — test/example secrets, dev-only or moderate/low CVEs. Never verdict-forcing.

test fixtureGeneric hardcoded secret13 in 6 files

src/main/resources/scripts/Authentication/db/data.sql:6, :10

:6 — -- Real passwo…8zQ' — non-production path

:10 — -- Real passwo…6mW' — non-production path

src/test/java/org/sasanlabs/internal/utility/PasswordHashingUtilsTest.java:41, :53

:41 — String rawPasswo…123"; — non-production path

:53 — String passwo…ord"; — non-production path

src/test/java/org/sasanlabs/service/vulnerability/idor/IDORLoginServiceTest.java:47, :83, :116

:47 — String rawPasswo…026"; — non-production path

:83 — String rawPasswo…026"; — non-production path

:116 — String rawPasswo…026"; — non-production path

src/test/java/org/sasanlabs/service/vulnerability/idor/IDORVulnerabilityTest.java:59, :163

:59 — String validToken …el2"; — non-production path

:163 — String invalidToken …ken"; — non-production path

src/test/java/org/sasanlabs/service/vulnerability/ldapInjection/LDAPInjectionVulnerabilityTest.java:57, :90

:57 — String username = "*)(uid=*", passwo…123"; — non-production path

:90 — String passwo…123"; — non-production path

src/test/java/org/sasanlabs/service/vulnerability/sessionManagement/SessionManagementServiceTest.java:23, :24

:23 — private static final String BAD_PASSWO…ord"; — non-production path

:24 — private static final String FIXED_TOKEN …ken"; — non-production path

advisoryPrivate Key blocksrc/main/java/org/sasanlabs/service/vulnerability/jwt/bean/JWTUtils.java:65

public static final String BEGIN_PRIVATE_KEY_TOKEN = "-----B…----"; — non-production path

AI audit for SasanLabs/VulnerableApp · all 14 dimensions · usually within 15 minutes*AI check for SasanLabs/VulnerableApp · all 14 areas · usually within 15 minutes*AI audit · SasanLabs/VulnerableApp · 14 dimensions · usually within 15 minutes*

Audit — your first Audit is free. After that, about $5.Needs a free GitHub or Google sign-inNeeds a free sign-in with GitHub or GoogleNeeds a free GitHub or Google sign-inThe free scan stays unlimitedYou can run the free scan as many times as you likeThe free scan stays unlimited

14 things we haven't looked at yet14 things we haven't checked yet14 things unaudited

Security logic, privacy, reliability, AI-generated-code risk and 10 more — unaudited, not clean.Security logic, privacy, reliability, AI-generated-code risk and 10 more — not checked yet, which is different from safe.Security, privacy, reliability, AI-generated-code risk, 10 more: unaudited, not clean.

The free scan reasons across none of these. Absence of findings is reported as unaudited, not safe. Opus 4.8 reads the code semantically and scores every one — with evidence, business impact, and a fix per finding.

The free scan doesn't look at any of these. If nothing is flagged here, that means it wasn't checked — not that it's safe. Opus 4.8 (the AI model behind the audit) reads and understands your code and scores every one of these — with evidence, the real-world impact, and a fix for each finding.

The free scan doesn't reason across these — unaudited, not safe. Opus 4.8 scores each, with evidence, impact, and a fix.

SecurityPriority: Core

Privacy & CompliancePriority: Core

Reliability & ResiliencePriority: Core

Code Quality & ArchitecturePriority: Important

AI / Vibe Coding RiskPriority: Important

Performance & ScalabilityPriority: Important

Infrastructure & DevOpsPriority: Important

Data LayerPriority: Important

Business & Product RiskPriority: Supporting

Developer ExperiencePriority: Supporting

Accessibility & UXPriority: Supporting

ObservabilityPriority: Supporting

Maintainability ForecastPriority: Specialized

IP & Novelty ExposurePriority: Specialized

Modules run (2)

Hardcoded Secret ScanDependency Vulnerability Scan

Hover a module for why it was selected. See every check nittim can run.

Scanned 330 of 461 files · SasanLabs/VulnerableApp
Dependency manifests: 1 Maven/Gradle manifest read (declared versions, advisory). Ruby dependencies detected — dependency-CVE scanning does not cover it yet; CVEs there are UNVERIFIED, not absent.

README badgeBadge for your project's readme fileREADME badge

nittim verdict badge for SasanLabs/VulnerableApp

[![nittim](https://nittim.com/api/badge/SasanLabs/VulnerableApp)](https://nittim.com)