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

appliedmindai/sam3-video-labelling-tool

https://github.com/appliedmindai/sam3-video-labelling-tool · scanned 2026-06-17 01:34 UTC (1 month, 2 weeks ago)

51 raw signals (0 security + 51 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -6.5 (diff) · 48 actionable findings from 1 signal source. 3 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
70.2
/100
Security checks
70
0 findings
System graph
70
77.8% cov · 48 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 0 Medium 7 Low 25 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 48 Crowd 0 Layer: Software 9 Frontend 1 Hardware 3 Security 2 Quality 33
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 70.2/100 with 77.8% coverage. It contains 1214 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 51 findings — concentrated in quality (36), software (9), hardware (3). Risk profile is low: 0 critical, 0 high, 7 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 32 of 48 actionable findings. 51 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/api.ts:32
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing ci, lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/app/services/video_processor.py:97
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: ci, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 49 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:22-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:2 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: pytorch/pytorch:2.5.1-cuda12.1-cudnn9-runtime
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:10 containersPinned dependencies
low System graph security security conf 1.00 Insecure pattern 'debug_true' in backend/run.py:46
Found a known-risky pattern (debug_true). Review and replace if possible.
backend/run.py:46 Debug true
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/app/services/gcs_sync.py:mark_dirty_safe, backend/app/services/gcs_sync.py:mark_dirty This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separ…
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: backend/app/services/pipeline.py:run, backend/app/services/pipeline.py:run, backend/app/services/pipeline.py:run, backend/app/services/pipeline.py:run This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai…
duplicatesduplication
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: scripts/user-guide-recorder/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
scripts/user-guide-recorder/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_import_v1` in backend/app/services/session_bundle.py:127
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `cache_old` in backend/app/config.py:186
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `cache_old` in backend/app/routes/session.py:261
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `cache_old` in backend/tests/test_atomic_install_paths.py:6
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `fake_copy` in backend/tests/test_pipeline.py:343
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: decorator
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/session_bundle.py:20
low System graph software Dead code conf 1.00 Possibly dead Python function: test_bidirectional_propagation
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/validate_sam3.py:129
low System graph software Dead code conf 1.00 Possibly dead Python function: test_edge_cases
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/validate_sam3.py:231
low System graph software Dead code conf 1.00 Possibly dead Python function: test_mask_deletion_no_stale_state
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/validate_sam3.py:176
low System graph software Dead code conf 1.00 Possibly dead Python function: test_mask_persistence_roundtrip
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/validate_sam3.py:261
low System graph software Dead code conf 1.00 Possibly dead Python function: test_multi_object
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/validate_sam3.py:67
low System graph software Dead code conf 1.00 Possibly dead Python function: test_object_switching
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/validate_sam3.py:92
low System graph software Dead code conf 1.00 Possibly dead Python function: test_propagation_continuity
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/validate_sam3.py:303
low System graph software Dead code conf 1.00 Possibly dead Python function: test_session_lifecycle
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/validate_sam3.py:207
low System graph quality Complexity conf 1.00 Very large file: backend/app/services/sam3_service.py (1934 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/tests/test_pipeline.py (1211 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/App.tsx (2498 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/c4ca802f-c7e4-4fab-8c7f-af10d62ebc93/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c4ca802f-c7e4-4fab-8c7f-af10d62ebc93/

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.