AkihikoWatanabe/paper_notes

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.

6 of your 17 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 80.46s for a 465.1 MB repo slow.
Repobility's analysis ran in 10.08s after the clone landed.

https://github.com/AkihikoWatanabe/paper_notes · scanned 2026-06-06 00:10 UTC (4 days, 2 hours ago) · 10 languages

56 raw signals (16 security + 40 graph) 11/13 scanners ran 76th percentile · Javascript · tiny (<2K LoC) System graph score 88 (lower by 13)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 2 hours ago · v2 · 31 actionable findings from 2 signal sources. 5 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 17 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	55.0	0.15	8.25
`security_score`	100.0	0.25	25.00
`testing_score`	70.0	0.20	14.00
`documentation_score`	67.0	0.15	10.05
`practices_score`	77.0	0.15	11.55
`code_quality`	68.0	0.10	6.80
Overall		1.00	75.6

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 5 Medium 6 Low 13 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 14 System graph 17 Crowd 0 Layer: Cicd 8 Quality 8 Software 9 Api 1 Hardware 3 Frontend 1 Security 1

Exclude dismissed / FP Exclude test files

Scan summary Quality grade B+ (76/100). Dimensions: security 100, maintainability 55. 16 findings (4 security). 1,308 lines analyzed.

Showing 24 of 31 actionable findings. 36 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.

high Security checks software dependencies conf 0.90 ✓ Repobility [MINED118] Dockerfile FROM `python:3.10-slim-bullseye` not pinned by digest: `FROM python:3.10-slim-bullseye` resolves the tag at build time. The registry CAN re-push a different image for the same tag, so every build is potentially different. Production images should pin to `image@sha256:...` for reproducibility + supply-chain integrity.

Replace with: `FROM python:3.10-slim-bullseye@sha256:<digest>`. Get the digest from `docker manifest inspect`. Re-pin via a scheduled bot (Renovate, Dependabot).

Dockerfile:1

low Security checks cicd CI/CD security conf 0.90 ✓ Repobility 6 occurrences GitHub Action is tag-pinned rather than SHA-pinned

[MINED115] Action `actions/checkout` pinned to mutable ref `@v2`: `uses: actions/checkout@v2` resolves at workflow-run time. Tags and branches can be re-pushed by the action owner; that made the tj-actions/changed-files compromise (2025) instantly affect ~23K repos. Pin to a 40-char commit SHA + lo…

2 files, 6 locations

.github/workflows/issue_correction.yml:13, 15 (4 hits)

.github/workflows/build_and_deploy.yml:13 (2 hits)

CI/CD securitySupply chainGitHub Actions

medium Security checks cicd CI/CD security conf 0.90 Docker build context has no .dockerignore

Add .dockerignore with at least .git, .env, private keys, dependency folders, build outputs, and local databases.

.dockerignore CI/CD securitycontainers

high Security checks cicd CI/CD security conf 0.82 Docker final stage has no non-root USER

Add a non-root USER in the final runtime stage after files and permissions are prepared.

Dockerfile:1 CI/CD securitycontainers

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 — .github/scripts/correct_issue.py:57

`requests.get(...)` 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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — generate_html.py:84

`requests.post(...)` 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.). Either auth lives in custom code, in a separate service, or is missing.

auth

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 6 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

high Security checks cicd CI/CD security conf 0.56 Compose service does not declare a runtime user

Set a non-root `user:` in Compose or ensure the final image stage has a non-root USER directive.

docker-compose.yaml CI/CD securitycontainers

high Security checks cicd CI/CD security conf 0.62 Compose service lacks no-new-privileges hardening

Add `security_opt: ["no-new-privileges:true"]` unless the service has a documented need for privilege escalation.

docker-compose.yaml CI/CD securitycontainers

low Security checks cicd CI/CD security conf 0.72 Dockerfile installs recommended OS packages

Add `--no-install-recommends` and explicitly list only packages the image needs.

Dockerfile:2 CI/CD securitycontainers

high Security checks cicd CI/CD security conf 0.72 Dockerfile keeps pip download cache

Use `pip install --no-cache-dir ...` in container builds.

Dockerfile:3 CI/CD securitycontainers

low Security checks cicd CI/CD security conf 0.74 Dockerfile leaves apt package indexes in the image layer

End the apt install layer with `rm -rf /var/lib/apt/lists/*`.

Dockerfile:2 CI/CD securitycontainers

low Security checks quality Quality conf 0.74 sitemap.xml contains non-HTTPS public URLs

Use HTTPS absolute URLs in sitemap <loc> entries.

docs/sitemap.xml

low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found

Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.

Deployment

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.10-slim-bullseye

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

Dockerfile:1 containersPinned dependencies

low System graph software Dead code conf 1.00 Possibly dead Python function: attach_pocket_tag