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

Scan timing: clone 1.65s · analysis 0.46s · 0.4 MB · GitHub preflight 530ms

nastya122622/my-angular-app

https://github.com/nastya122622/my-angular-app.git · scanned 2026-05-25 16:51 UTC (1 week, 3 days ago) · 10 languages

30 findings (16 legacy + 14 scanner) 15th percentile · Typescript · small (2-20K LoC) Scanner says 95 (lower by 43)

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

Complete repo analysis

Last scanned 1 week, 3 days ago · v2 · 23 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
Combined
89.3
/100
Repobility
83
16 legacy
9-layer
95
77.8% cov · 7 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 100.0 0.15 15.00
security_score 97.0 0.25 24.25
testing_score 0.0 0.20 0.00
documentation_score 0.0 0.15 0.00
practices_score 42.0 0.15 6.30
code_quality 67.4 0.10 6.74
Overall 1.00 52.3
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 4 Medium 6 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 16 9-layer 7 Crowd 0 Layer: Quality 14 Security 4 Software 2 Api 1 Frontend 1 Cicd 1

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 9 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
9 matching findings on this repo
  • medium Public web service has no security.txt .well-known/security.txt
  • medium Public web app has no Content Security Policy index.html
  • low Public web app has no humans.txt humans.txt
  • low Public web app has no sitemap sitemap.xml
  • low Public web app has no robots.txt robots.txt
  • low Duplicated implementation block across source files src/app/components/self-development/ self-develop…:84
  • low Duplicated implementation block across source files src/app/components/practice/practice.component.ts:115
  • low Duplicated implementation block across source files src/app/components/courses/courses.component.ts:39
  • low Duplicated implementation block across source files src/app/components/about/about.component.ts:147
View all fragile runtime findings →
Config drift 2 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
2 matching findings on this repo
  • medium No CI/CD configuration found
  • low File has no detected symbols: src/app/app.config.ts
View all config drift findings →
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/f4cdfe3c-1d66-40c2-9943-7cf66fb1c69b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f4cdfe3c-1d66-40c2-9943-7cf66fb1c69b/

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.