expressjs/body-parser

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.

Scan timing: clone 2.93s · analysis 0.15s · 0.2 MB · GitHub preflight 448ms

https://github.com/expressjs/body-parser · scanned 2026-05-20 05:23 UTC (2 weeks, 2 days ago) · 10 languages

19 findings (7 legacy + 12 scanner) 87th percentile · Javascript · small (2-20K LoC) Scanner says 94 (lower by 9)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 2 days ago · v2 · 13 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`	100.0	0.15	15.00
`security_score`	98.8	0.25	24.70
`testing_score`	87.0	0.20	17.40
`documentation_score`	68.0	0.15	10.20
`practices_score`	79.0	0.15	11.85
`code_quality`	66.8	0.10	6.68
Overall		1.00	85.8

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 5 Medium 3 Low 2 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 7 9-layer 6 Crowd 0 Layer: Security 3 Quality 5 Software 1 Api 1 Frontend 2 Cicd 1

Exclude dismissed / FP Exclude test files

Scan summary Repository scanned at 94.4/100 with 66.7% coverage. It contains 84 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 6 findings — concentrated in frontend (2), software (1), api (1). Risk profile is low: 0 critical, 0 high, 2 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

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

medium Legacy security auth conf 0.92 [AUC001] No Repobility access matrix policy found: The repository uses web/API frameworks but does not define .repobility/access.yml or equivalent authorization documentation.

The repository uses web/API frameworks but does not define .repobility/access.yml or equivalent authorization documentation.

authlegacy

medium 9-layer cicd supply-chain 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/scorecard.yml supply-chaingithub-actionsleast-privilege

medium 9-layer 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.

coverageauth

low Legacy security auth conf 0.76 [AUC005] No authorization-focused tests detected: No test files with common authorization, ownership, 403, admin, or super_admin assertions were found.

No test files with common authorization, ownership, 403, admin, or super_admin assertions were found.

authlegacy

low 9-layer software dead-code-candidate conf 1.00 File has no detected symbols: test/body-parser.js

Source file with no class/function declarations — possible config, dead code, or scratch file.

dead-code-candidate

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/ec217d79-feae-4f6e-b5f9-de188e904e4b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ec217d79-feae-4f6e-b5f9-de188e904e4b/

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.