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.

nick-aply/teamfeed-server

https://github.com/nick-aply/teamfeed-server · scanned 2026-06-16 04:34 UTC (1 month, 4 weeks ago)

32 raw signals (0 security + 32 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 4 weeks ago · v1 · 32 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: layer: security × excluding tests × Reset all
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 62.1/100 with 77.8% coverage. It contains 39 nodes across 19 cross-layer flows, written primarily in mixed languages. Engine surfaced 32 findings — concentrated in api (20), quality (8), frontend (2). Risk profile is high: 2 critical, 1 high, 2 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

critical System graph security security conf 1.00 Insecure pattern 'private_key_in_repo' in server.js:7
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
server.js:7 Private key in repo
critical System graph security Secrets conf 1.00 Possible secret in server.js
Detected pattern matching private_key. Rotate the credential and move to a secret manager.
server.js:6
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/0ce331fa-9358-4017-a2d0-804a4716db7c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0ce331fa-9358-4017-a2d0-804a4716db7c/

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.