apache/nifi-minifi-cpp

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.

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

Scan timing: clone 5.09s · analysis 44.55s · 13.8 MB · GitHub API rate-limit (preflight)

https://github.com/apache/nifi-minifi-cpp · scanned 2026-06-05 12:57 UTC (5 days, 9 hours ago) · 10 languages

673 raw signals (141 security + 532 graph) 25th percentile · Cpp · large (100-500K LoC) System graph score 67 (lower by 10)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 197 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	40.0	0.15	6.00
`security_score`	28.6	0.25	7.15
`testing_score`	80.0	0.20	16.00
`documentation_score`	75.0	0.15	11.25
`practices_score`	70.0	0.15	10.50
`code_quality`	68.3	0.10	6.83
Overall		1.00	57.7

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 7 Medium 13 Low 41 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 44 System graph 197 Crowd 0 Layer: Security 13 Software 23 Cicd 7 Quality 190 Frontend 2 Network 2 Hardware 4

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 4 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

4 matching findings on this repo

low Near-duplicate function bodies in 7 places repo-level
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 4 places

View all duplicates & near-duplicates findings →

Commented-out code 154 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (6 lines) in bootstrap/system_dependency.py:1
info Commented-code block (6 lines) in bootstrap/cli.py:1
info Commented-code block (6 lines) in bootstrap/cmake_parser.py:1
info Commented-code block (6 lines) in bootstrap/minifi_option.py:1
info Commented-code block (6 lines) in bootstrap/main.py:1
info Commented-code block (6 lines) in bootstrap/package_manager.py:1
info Commented-code block (6 lines) in extensions/grafana-loki/tests/features/enviro…
info Commented-code block (6 lines) in extensions/grafana-loki/tests/features/resour…
info Commented-code block (6 lines) in extensions/grafana-loki/tests/features/steps/…
info Commented-code block (6 lines) in extensions/grafana-loki/tests/features/contai…
info Commented-code block (6 lines) in extensions/grafana-loki/tests/features/contai…
info Commented-code block (6 lines) in extensions/gcp/tests/features/environment.py:1

View all commented-out code findings →

Config drift 1 finding

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

1 matching finding on this repo

info Commented-code block (6 lines) in behave_framework/src/minifi_behave/steps/conf…

View all config drift findings →

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/aa213b45-01fc-482a-a2e9-e6ada224fccf/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/aa213b45-01fc-482a-a2e9-e6ada224fccf/

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.