tobi/delayed_job
Database backed asynchronous priority queue -- Extracted from Shopify
- Repository: https://github.com/tobi/delayed_job
- Commit:
719b628bdd54566f80ae3a99c4a02dd39d386c07 - Generated: 2026-11-13T23:29:56+00:00
- Scorer 0.1.0, scoring prov-4+qual-2+sec-2, report schema v2
Scores
| Pillar | Score | Signal | Confidence | Coverage |
|---|---|---|---|---|
| AI provenance (estimated AI-generated share) | 0 | none-detected | 57% | 100% |
| Code quality | 83 | strong | 90% | 100% |
| Security | 67 | weak | 85% | 100% |
AI provenance
No AI attribution or AI-consistent velocity signals detected.
- Explicitly attributed share (lower bound): 0.0%
- Unattributed share in AI-consistent velocity bursts: 0.0%
- Estimated AI-generated share: 0.0%
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2008-07 | 68 | 0% |
| 2008-09 | 230 | 0% |
| 2008-10 | 72 | 0% |
| 2008-11 | 545 | 0% |
| 2008-12 | 31 | 0% |
| 2009-01 | 2 | 0% |
| 2009-02 | 36 | 0% |
| 2009-03 | 115 | 0% |
| 2009-10 | 5 | 0% |
| 2009-12 | 37 | 0% |
| 2010-09 | 1 | 0% |
| 2011-03 | 16 | 0% |
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 strong: test-to-source ratio 1.18, no CI test run detected; 0% of function code in complex or long functions; 0% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 100 |
| Duplication | 100 |
| Code smells (Opengrep) | 100 |
| Tests and CI | 55 |
| Documentation | 65 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 37; mean complexity 2.0, 90th percentile 4; 0 complex and 0 long functions
- Duplicated lines: 0.0% of 297 compared
- Tests: 547 test lines for 464 source lines (ratio 1.18); CI test commands: none detected; 60% of recent source commits also change tests
- Docs missing or thin: contributing, changelog
Security
Security posture is weak: 2 high-severity SAST findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 59 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
- Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | opengrep/ruby.lang.security.bad-deserialization-yaml: Unsafe deserialization from YAML. Objects in Ruby can be serialized into strings, then later loaded from strings. However, uses of load and object_load can cause remote code execution. Loading user input with YAML can potentially be dangerous. Use JSON in a secure fashion instead. However, loading Y [confidence low] |
lib/delayed/job.rb:223 |
| high | opengrep/ruby.lang.security.bad-deserialization-yaml: Unsafe deserialization from YAML. Objects in Ruby can be serialized into strings, then later loaded from strings. However, uses of load and object_load can cause remote code execution. Loading user input with YAML can potentially be dangerous. Use JSON in a secure fashion instead. However, loading Y [confidence low] |
lib/delayed/job.rb:230 |
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
- Source lines: 464; test lines: 547
| Language | Lines |
|---|---|
| Ruby | 1,011 |