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

lensesio/fast-data-dev

https://github.com/lensesio/fast-data-dev · scanned 2026-05-16 00:58 UTC (2 weeks, 6 days ago) · 10 languages

33 findings (24 legacy + 9 scanner) 28th percentile · Javascript · tiny (<2K LoC) Scanner says 93 (lower by 43)

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

Complete repo analysis

Last scanned 2 weeks, 6 days ago · v1 · 23 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
75.0
/100
Repobility
57
23 legacy
9-layer
93
100.0% cov · 0 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-14-v3
Component Sub-score Weight Contribution
structure_score 45.0 0.15 6.75
security_score 75.0 0.25 18.75
testing_score 0.0 0.20 0.00
documentation_score 60.0 0.15 9.00
practices_score 50.0 0.15 7.50
code_quality 80.0 0.10 8.00
Overall 1.00 50.0
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 8 Medium 7 Low 4 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 23 9-layer 0 Crowd 0 Layer: Cicd 22 Quality 1
Scan summary Repository scanned at 93.3/100 with 100.0% coverage. It contains 68 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 0 findings. Risk profile is low: 0 critical, 0 high, 0 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

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

high Legacy cicd docker conf 0.90 Database service has no persistent data volume
Database containers store data in the writable container layer unless a volume or bind mount is attached to the image's data directory. Recreating the container can lose state.
examples/fdd-mongo/docker-compose.yml:21 dockerlegacy
high Legacy cicd docker conf 0.90 Database service has no persistent data volume
Database containers store data in the writable container layer unless a volume or bind mount is attached to the image's data directory. Recreating the container can lose state.
examples/fdd-mongo/docker-compose.yml:14 dockerlegacy
high Legacy cicd docker conf 0.84 Database service publishes a host port
Publishing database ports to the host increases exposure. Internal Compose networking usually only needs expose, not ports.
examples/fdd-mongo/docker-compose.yml:14 dockerlegacy
high Legacy cicd docker conf 0.84 Database service publishes a host port
Publishing database ports to the host increases exposure. Internal Compose networking usually only needs expose, not ports.
examples/fdd-mongo/docker-compose.yml:2 dockerlegacy
high Legacy cicd docker conf 0.84 Database service publishes a host port
Publishing database ports to the host increases exposure. Internal Compose networking usually only needs expose, not ports.
examples/fdd-acls/docker-compose.yml:2 dockerlegacy
high Legacy cicd docker conf 0.86 Docker build secret exposed through ARG
Build arguments can appear in image history or provenance. Secret material should be passed with BuildKit secret mounts.
Dockerfile:89 dockerlegacy
high Legacy cicd docker conf 0.86 Docker build secret exposed through ARG
Build arguments can appear in image history or provenance. Secret material should be passed with BuildKit secret mounts.
Dockerfile:88 dockerlegacy
medium Legacy cicd docker conf 0.94 Compose service `lenses-dev` image uses the latest tag
The latest tag is mutable and can change without a code review, producing different images from the same source.
examples/fdd-mongo/docker-compose.yml:2 dockerlegacy
medium Legacy cicd docker conf 0.56 Compose service contains a literal secret environment value
Literal secrets in Compose files are committed to source and exposed through container inspection.
examples/fdd-acls/docker-compose.yml:2 dockerlegacy
medium Legacy cicd docker conf 0.88 Database service has no healthcheck
Compose starts dependent containers in dependency order, but it does not wait for a database to be ready unless a healthcheck is defined and dependents use service_healthy.
examples/fdd-mongo/docker-compose.yml:21 dockerlegacy
medium Legacy cicd docker conf 0.88 Database service has no healthcheck
Compose starts dependent containers in dependency order, but it does not wait for a database to be ready unless a healthcheck is defined and dependents use service_healthy.
examples/fdd-mongo/docker-compose.yml:14 dockerlegacy
medium Legacy cicd docker conf 0.74 Database service has no persistent data volume
Database containers store data in the writable container layer unless a volume or bind mount is attached to the image's data directory. Recreating the container can lose state.
examples/fdd-mongo/docker-compose.yml:2 dockerlegacy
medium Legacy cicd docker conf 0.74 Database service has no persistent data volume
Database containers store data in the writable container layer unless a volume or bind mount is attached to the image's data directory. Recreating the container can lose state.
examples/fdd-acls/docker-compose.yml:2 dockerlegacy
medium Legacy cicd docker conf 0.90 Docker build context has no .dockerignore
Without .dockerignore, build context can include source history, local env files, dependencies, and generated artifacts.
.dockerignore dockerlegacy
high Legacy cicd docker conf 0.82 Docker final stage has no non-root USER
Docker images run as root unless the image or Dockerfile switches to a non-root user.
Dockerfile:220 dockerlegacy
low Legacy cicd docker conf 0.72 Database service has no healthcheck
Compose starts dependent containers in dependency order, but it does not wait for a database to be ready unless a healthcheck is defined and dependents use service_healthy.
examples/fdd-mongo/docker-compose.yml:2 dockerlegacy
low Legacy cicd docker conf 0.72 Database service has no healthcheck
Compose starts dependent containers in dependency order, but it does not wait for a database to be ready unless a healthcheck is defined and dependents use service_healthy.
examples/fdd-acls/docker-compose.yml:2 dockerlegacy
low Legacy cicd docker conf 0.72 Dockerfile installs recommended OS packages
Installing recommended packages often pulls in unnecessary runtime surface area.
Dockerfile:232 dockerlegacy
low Legacy cicd docker conf 0.72 Dockerfile installs recommended OS packages
Installing recommended packages often pulls in unnecessary runtime surface area.
Dockerfile:7 dockerlegacy
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/3af2bca0-4d6c-49c6-90f4-971e0cc6fd30/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/3af2bca0-4d6c-49c6-90f4-971e0cc6fd30/

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.