RepoTrust

datachain-ai/datachain

The Context Layer for unstructured data: typed, versioned datasets over S3, GCS, Azure

https://github.com/datachain-ai/datachain · commit 8b7fe3202ba8 · scored 2026-11-14 · scoring prov-4+qual-2+sec-2

RepoTrust ai badge RepoTrust quality badge RepoTrust security badge

Dispute this score or request a re-score Full report JSON

Scores

Pillar Score Signal Confidence Coverage
AI provenance (estimated AI-generated share) 9 explicit 95% 100%
Code quality 76 adequate 90% 100%
Security 63 weak 85% 100%

AI provenance

Explicit AI attribution on 9% of first-party code added; an estimated 9% including velocity signals.

AI tool Attributed commits Lines added
Claude Code 87 15,643
GitHub Copilot coding agent 21 2,873
Cursor agent 3 1,039
OpenAI Codex 1 195

Current source lines last changed by AI-attributed commits: 6,165 of 60,658.

Findings per 1,000 lines AI-attributed Other Ratio
Quality 2.595 2.147 1.21x
Security 0.649 0.312 2.08x
Month Lines added Attributed to AI
2025-12 5,326 4%
2026-01 2,640 0%
2026-02 6,909 33%
2026-03 10,403 7%
2026-04 10,375 0%
2026-05 4,428 3%
2026-06 5,246 4%
2026-07 8,021 17%
2026-08 3,074 50%
2026-09 1,517 39%
2026-10 15,329 32%
2026-11 15,811 42%

Evidence

AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.

Code quality

Code quality is adequate: test-to-source ratio 1.42, CI runs tests; 14% of function code in complex or long functions; 5% duplicated lines. Weakest area: lint.

Area Score
Complexity (lizard) 66
Duplication 75
Code smells (Opengrep) 55
Tests and CI 100
Documentation 80
Type safety 60
Process (Scorecard review/maintenance) n/a

Most complex functions:

Security

Security posture is weak: 8 high-severity SAST findings; 37 high-severity workflow issues. Weakest area: ci actions.

Area Score
Secrets (gitleaks, tree + history) 77
Static analysis (Opengrep) 94
Vulnerable dependencies (OSV) n/a
CI workflows (zizmor) 0
Posture (policy, updates, signing, lockfiles) 60
OpenSSF Scorecard n/a

Top findings

Severity Finding Location
high opengrep/python.lang.security.audit.dangerous-system-call-audit: Found dynamic content used in a system call. This is dangerous if external data can reach this function call because it allows a malicious actor to execute commands. Use the 'subprocess' module instead, which is easier to use without accidentally exposing a command injection vulnerability. [confidence low] docs/api_hooks.py:42
high opengrep/python.lang.security.use-defused-xml: The Python documentation recommends using defusedxml instead of xml because the native Python xml library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause denial of service. [confidence low] src/datachain/client/azure.py:8
high opengrep/python.lang.security.audit.dangerous-asyncio-create-exec-audit: Detected 'create_subprocess_exec' function without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] src/datachain/client/listing_worker.py:83
high opengrep/python.lang.security.use-defused-xml: The Python documentation recommends using defusedxml instead of xml because the native Python xml library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause denial of service. [confidence low] src/datachain/client/s3.py:7
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] src/datachain/lib/video.py:616
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] src/datachain/query/dataset.py:1010
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] src/datachain/sql/sqlite/base.py:779
high opengrep/python.sqlalchemy.security.audit.avoid-sqlalchemy-text: sqlalchemy.text passes the constructed SQL statement to the database mostly unchanged. This means that the usual SQL injection protections are not applied and this function is vulnerable to SQL injection if user input can reach here. Use normal SQLAlchemy operators (such as or_, and_, etc.) to const [confidence medium] src/datachain/testing.py:25
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/actions/install-ffmpeg/action.yml:17
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/actions/install-ffmpeg/action.yml:37
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/benchmarks.yml:21
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/benchmarks.yml:23
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/benchmarks.yml:28
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/codspeed.yml:20
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/codspeed.yml:25
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/codspeed.yml:30
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/codspeed.yml:40
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/codspeed.yml:49
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/codspeed.yml:54
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/codspeed.yml:59
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/codspeed.yml:72
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/release.yml:20
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/release.yml:25
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/release.yml:30
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/release.yml:39

Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.

Repository profile

Language Lines
Python 146,657

Embed a badge

Maintainers can show these in a README. Badges update when the repository is re-scored.

[![RepoTrust ai](https://repotrust.synapticcyber.com/badge/github.com/datachain-ai/datachain/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/datachain-ai/datachain/)
[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/datachain-ai/datachain/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/datachain-ai/datachain/)
[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/datachain-ai/datachain/security.svg)](https://repotrust.synapticcyber.com/r/github.com/datachain-ai/datachain/)