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.
Sign up free Scan another repo
126 of your 215 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 7.34s · analysis 17.45s · 17.9 MB · GitHub API rate-limit (preflight)

deepset-ai/haystack-core-integrations

https://github.com/deepset-ai/haystack-core-integrations · scanned 2026-06-05 13:26 UTC (5 days, 7 hours ago) · 10 languages

642 raw signals (198 security + 444 graph) 17th percentile · Python · large (100-500K LoC) System graph score 79 (lower by 16)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
62.6
/100
Security checks
47
75 findings
System graph
79
100.0% cov · 131 findings
Critical
8
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 37.0 0.25 9.25
testing_score 100.0 0.20 20.00
documentation_score 90.0 0.15 13.50
practices_score 74.0 0.15 11.10
code_quality 31.5 0.10 3.15
Overall 1.00 63.0
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 8 High 13 Medium 12 Low 103 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 75 System graph 131 Crowd 0 Layer: Cicd 15 Quality 112 Software 66 Security 10 Api 1 Hardware 1 Frontend 1

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

#1
Possible secret in integrations/alloydb/src/haystack_integrations/document_stores/alloydb/document_store.py
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 integrations/alloydb/src/haystack_integrations/document_stores/alloydb/document_store.py:91; move to env var / secrets manager.
integrations/alloydb/src/haystack_integrations/document_stores/alloydb/document_store.py:91
#2
Possible secret in integrations/weaviate/src/haystack_integrations/document_stores/weaviate/auth.py
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 integrations/weaviate/src/haystack_integrations/document_stores/weaviate/auth.py:27; move to env var / secrets manager.
integrations/weaviate/src/haystack_integrations/document_stores/weaviate/auth.py:27
#3
Possible secret in integrations/snowflake/src/haystack_integrations/components/retrievers/snowflake/auth.py
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 integrations/snowflake/src/haystack_integrations/components/retrievers/snowflake/auth.py:25; move to env var / secrets manager.
integrations/snowflake/src/haystack_integrations/components/retrievers/snowflake/auth.py:25
#4
Possible secret in integrations/snowflake/src/haystack_integrations/components/retrievers/snowflake/snowflake_table_retriever.py
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 integrations/snowflake/src/haystack_integrations/components/retrievers/snowflake/snowflake_table_retriever.py:238; move to env var / secrets manager.
integrations/snowflake/src/haystack_integrations/components/retrievers/snowflake/snowflake_table_retriever.py:238
#5
pull_request_target workflow appears to check out untrusted PR code
GapSeverity.HIGH Layer.CICD score 0.375
Why: high severity
.github/workflows/CI_docstring_labeler.yml
#6
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/amazon_sagemaker.yml
#7
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/falkordb.yml
#8
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/nvidia.yml
#9
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/paddleocr.yml
#10
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/firecrawl.yml

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/45850fae-6fe7-4e53-90fd-1a07f571b585/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/45850fae-6fe7-4e53-90fd-1a07f571b585/

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.