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.

blanpa/node-red-contrib-s7-suite

https://github.com/blanpa/node-red-contrib-s7-suite · scanned 2026-06-17 01:41 UTC (1 month, 1 week ago)

6 raw signals (0 security + 6 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ +14.7 (diff) · 5 actionable findings from 1 signal source. 1 repeated signal grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 5 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

Exclude dismissed / FP Exclude test files

6 healthy

GET /s7-suite/browse/:id

healthy

endpoint

auth

GET /s7-suite/connection-state/:id

healthy

endpoint

auth

GET /s7-suite/plc-defaults

healthy

endpoint

auth

GET /s7-suite/snap7-available

healthy

endpoint

auth

POST /s7-suite/cfg-import

healthy

endpoint

auth

POST /s7-suite/tia-xml-import

healthy

endpoint

auth

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/8f72d14a-fe8f-424a-9e2a-5d1ae856d063/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8f72d14a-fe8f-424a-9e2a-5d1ae856d063/

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.