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.
162 of your 259 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 137.27s for a 618.7 MB repo slow.
  • Repobility's analysis ran in 293.76s after the clone landed.

nodejs/node

https://github.com/nodejs/node · scanned 2026-06-05 05:18 UTC (8 hours, 28 minutes ago) · 10 languages

11114 findings (246 legacy + 10868 scanner) 11/13 scanners ran 60th percentile · Javascript · huge (>500K LoC) Scanner says 66 (higher by 22)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 8 hours, 28 minutes ago · v2 · 5680 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
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 92.0 0.20 18.40
documentation_score 88.0 0.15 13.20
practices_score 87.0 0.15 13.05
code_quality 56.0 0.10 5.60
Overall 1.00 88.0
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

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in deps/npm/lib/commands/profile.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in deps/npm/lib/commands/profile.js:168; move to env var / secrets manager.
deps/npm/lib/commands/profile.js:168
#2
Possible secret in deps/npm/lib/commands/profile.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in deps/npm/lib/commands/profile.js:195; move to env var / secrets manager.
deps/npm/lib/commands/profile.js:195
#3
Possible secret in deps/npm/lib/utils/read-user-info.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in deps/npm/lib/utils/read-user-info.js:10; move to env var / secrets manager.
deps/npm/lib/utils/read-user-info.js:10
#4
Possible secret in deps/npm/lib/utils/auth.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in deps/npm/lib/utils/auth.js:53; move to env var / secrets manager.
deps/npm/lib/utils/auth.js:53
#5
Possible secret in deps/npm/lib/utils/auth.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in deps/npm/lib/utils/auth.js:89; move to env var / secrets manager.
deps/npm/lib/utils/auth.js:89
#6
Insecure pattern 'eval_used' in lib/internal/process/execution.js:79
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
lib/internal/process/execution.js:79
#7
Insecure pattern 'eval_used' in lib/internal/repl/completion.js:421
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
lib/internal/repl/completion.js:421
#8
Insecure pattern 'exec_used' in lib/internal/debugger/inspect_repl.js:98
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
lib/internal/debugger/inspect_repl.js:98
#9
Insecure pattern 'eval_used' in lib/internal/modules/esm/loader.js:249
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
lib/internal/modules/esm/loader.js:249
#10
Insecure pattern 'exec_used' in lib/internal/per_context/primordials.js:615
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
lib/internal/per_context/primordials.js:615

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/f9fcf18e-aacd-473f-8572-887b663f1bea/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f9fcf18e-aacd-473f-8572-887b663f1bea/

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.