base/node

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.

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

Scan timing: clone 1.22s · analysis 0.38s · 0.1 MB · GitHub API rate-limit (preflight)

https://github.com/base/node · scanned 2026-06-05 08:42 UTC (5 days, 19 hours ago) · 10 languages

31 raw signals (13 security + 18 graph) 10th percentile · Unknown · System graph score 68 (lower by 8)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 9 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	30.0	0.15	4.50
`security_score`	42.9	0.25	10.72
`testing_score`	70.0	0.20	14.00
`documentation_score`	75.0	0.15	11.25
`practices_score`	77.0	0.15	11.55
`code_quality`	80.0	0.10	8.00
Overall		1.00	60.0

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

Exclude dismissed / FP Exclude test files

Scan summary Quality grade C+ (60/100). Dimensions: security 43, maintainability 30. 13 findings (3 security).

Showing 17 of 19 actionable findings. 22 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.

critical Security checks security Security .env file committed to repository

Remove .env from version control: git rm --cached .env. Add '.env' to .gitignore. Rotate all exposed credentials.

.env

critical Security checks security secrets conf 1.00 [SEC009] .env File Committed: .env file with secrets committed to repository.

Add .env to .gitignore. Rotate all exposed credentials.

.env

critical Security checks security secrets conf 0.95 Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

Gitleaks detected a committed secret or credential pattern.

.env.mainnet:24

critical Security checks security secrets conf 0.95 Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

Gitleaks detected a committed secret or credential pattern.

.env.sepolia:24

high Security checks software dependencies conf 0.90 ✓ Repobility 2 occurrences Dockerfile FROM `public.ecr.aws/docker/library/rust (no tag)` not pinned by digest

`FROM public.ecr.aws/docker/library/rust (no tag)` 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.

lines 2, 41

Dockerfile:2, 41 (2 hits)

high System graph security Secrets conf 1.00 .env file present in repo: .env

A raw .env file is in the working tree. Verify it isn't committed and that secrets are in a vault.

Config

high Security checks cicd CI/CD security 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:42 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 cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions

CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.

.github/workflows/docker.yml CI/CD securitySupply chainGithub actions

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

low Security checks cicd CI/CD security conf 0.72 .dockerignore misses sensitive defaults

.dockerignore exists but does not cover common secret or VCS patterns.

.dockerignore CI/CD securitycontainers

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

If the image does not define USER internally, this service may run as root.

lines 1, 17

docker-compose.yml:1, 17 (2 hits)

CI/CD securitycontainers

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

no-new-privileges prevents processes from gaining additional privileges through setuid binaries or file capabilities.

lines 1, 17

docker-compose.yml:1, 17 (2 hits)

CI/CD securitycontainers

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

Installing recommended packages often pulls in unnecessary runtime surface area.

Dockerfile:44 CI/CD securitycontainers

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: public.ecr.aws/docker/library/rust:${RUST_VERSION}-trixie

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: ubuntu:24.04

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

Dockerfile:41 containersPinned dependencies

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/1297c01f-7581-4000-a049-19269cee9cf7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1297c01f-7581-4000-a049-19269cee9cf7/

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.