Leaderboard github.com
asmuth/recommendify
Generate recommendations using collaborative filtering
AI provenance
0%
none-detected
- Confidence
- 65%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
60/100
weak
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
59/100
weak
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
AI provenance
0% none-detected
No AI attribution or AI-consistent velocity signals detected.
How the score is built
- Explicitly attributed share0%
- Unattributed share in AI-pace bursts0%
- Estimated AI-generated share0%
- AI tool configuration files0
- Work sessions at AI pace0
- Releases at AI pacenot measured
- Coding-style index (1.0+ means possible)0.00
Lines added per month all AI-attributed share
- 2012-011,492 · 0% AI
- 2012-02879 · 0% AI
- 2012-03124 · 0% AI
Evidence by analyzer
Explicit AI attributionok
- attributed_commit_share
- 0.0%
- attributed_commits
- 0
- attributed_loc
- 0
- attributed_loc_share
- 0.0%
- commits
- 154
- effective_loc
- 2,495
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 0
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 90.10
- measured_loc
- 2,495
- median_loc_per_hour
- 78.13
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 0
- pre_ai_era_bursts
- 0
- pre_ai_era_measured_loc
- 2,495
- work_units
- 26
Release velocityskipped
Coding styleok
- count:assistant_voice
- 0
- count:emoji_in_code
- 0
- count:narrated_steps
- 0
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 0
- files:narrated_steps
- 0
- files:placeholder
- 0
- index
- 0
- lines_scanned
- 855
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0
- per_kloc:placeholder
- 0
Code quality
60 weak
Code quality is weak: test-to-source ratio 0.80, no CI test run detected; 28% of function code in complex or long functions; 0% duplicated lines. Weakest area: lint.
How the score is built
- Complexity44
- Duplication100
- Lint and smells37
- Tests and CI70
- Documentation40
- Type safetynot measured
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok1 item
- complex_functions
- 1
- function_nloc
- 505
- functions
- 78
- long_functions
- 1
- many_param_functions
- 0
- mean_ccn
- 1.78
- p90_ccn
- 2
- risky_nloc_share
- 27.7%
Duplication (jscpd)ok
- compared_lines
- 529
- duplicated_lines
- 0
- duplicated_share
- 0.0%
- files
- 20
Lintok
- category:correctness
- 4
- findings
- 4
- scanned_lines
- 855
- weighted_findings
- 4
Tests and CIok1 item
- CI config: .travis.yml
.travis.yml
- check:ci_present
- yes
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- yes
- check:test_ratio
- yes
- check:tests_cochange
- yes
- ci_files
- 1
- cochange_commits
- 88
- cochange_share
- 35.2%
- source_lines
- 855
- test_lines
- 687
- test_ratio
- 0.80
Documentationok1 item
- README.md
README.md
- check:changelog
- no
- check:contributing
- no
- check:license
- no
- check:readme
- yes
- readme_lines
- 98
Type safetyskipped
Security
59 weak
Security posture is weak: 1 high-severity SAST findings. Weakest area: posture.
How the score is built
- Secrets100
- Static analysis (SAST)38
- Vulnerable dependenciesnot measured
- CI workflowsnot measured
- Security posture0
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesskipped
no registry dependencies declared
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 0
- secrets_nonprod
- 0
Static analysis (opengrep)ok
- findings
- 9
- findings_high
- 1
- findings_low
- 0
- findings_medium
- 8
- parse_errors
- 0
- scanned_lines
- 855
- weighted_findings
- 2.75
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok1 item
- Gemfile has no lockfile alongside it (unpinned dependencies)
Gemfile
- check:dependency_updates
- no
- check:lockfiles
- no
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 0.0%
- unpinned_manifests
- 1
Release downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
1 high12 medium
13 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| high | opengrep/ruby.lang.security.model-attributes-attr-accessible |
doc/example.rb:9 | Checks for models that do not use attr_accessible. This means there is no limiting of which variables can be manipulated through mass assignment. For newer Rails applications, parameters should be allowlisted using strong parameters.... | Static analysis (opengrep) |
| medium | opengrep/c.lang.correctness.incorrect-use-ato-fn |
ext/recommendify.c:130 | Avoid the 'ato*()' family of functions. Their use can lead to undefined behavior, integer overflows, and lack of appropriate error handling. Instead prefer the 'strtol*()' family of functions. | Lint |
| medium | opengrep/c.lang.correctness.incorrect-use-ato-fn |
ext/recommendify.c:166 | Avoid the 'ato*()' family of functions. Their use can lead to undefined behavior, integer overflows, and lack of appropriate error handling. Instead prefer the 'strtol*()' family of functions. | Lint |
| medium | opengrep/c.lang.correctness.incorrect-use-ato-fn |
ext/recommendify.c:68 | Avoid the 'ato*()' family of functions. Their use can lead to undefined behavior, integer overflows, and lack of appropriate error handling. Instead prefer the 'strtol*()' family of functions. | Lint |
| medium | opengrep/c.lang.correctness.incorrect-use-ato-fn |
ext/recommendify.c:95 | Avoid the 'ato*()' family of functions. Their use can lead to undefined behavior, integer overflows, and lack of appropriate error handling. Instead prefer the 'strtol*()' family of functions. | Lint |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
ext/recommendify.c:129 | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-strcat-fn |
ext/recommendify.c:154 | Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-strcat-fn |
ext/recommendify.c:155 | Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-printf-fn |
ext/recommendify.c:49 | Avoid using user-controlled format strings passed into 'sprintf', 'printf' and 'vsprintf'. These functions put you at risk of buffer overflow vulnerabilities through the use of format string exploits. Instead, use 'snprintf' and... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
ext/recommendify.c:66 | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
ext/recommendify.c:70 | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
ext/recommendify.c:76 | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows,... | Static analysis (opengrep) |
| medium | opengrep/ruby.lang.security.dangerous-subshell |
lib/recommendify/jaccard_input_matrix.rb:37 | Detected non-static command inside `...`. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. [confidence low] | Static analysis (opengrep) |
Tools and coverage
Every analyzer that ran on this commit. A failed or skipped tool is a coverage gap: its share of the score is left out and the coverage figure drops.
| Analyzer | Pillar | Status | Version | Findings | Note |
|---|---|---|---|---|---|
| AI tool configuration | AI provenance | ok | signatures-v1 | 0 | |
| Explicit AI attribution | AI provenance | ok | signatures-v1 | 0 | |
| Release velocity | AI provenance | skipped | — | 0 | |
| Coding style | AI provenance | ok | — | 0 | |
| Commit velocity | AI provenance | ok | prov-4 | 0 | |
| Complexity (lizard) | Code quality | ok | lizard 1.25.1 | 0 | |
| Documentation | Code quality | ok | — | 0 | |
| Duplication (jscpd) | Code quality | ok | repotrust-dup-w6 | 0 | |
| Lint | Code quality | ok | opengrep 1.33.1; rules f1d2b562b414 | 4 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | skipped | — | 0 | |
| CI workflows (zizmor) | Security | skipped | — | 0 | |
| Dependencies (osv-scanner) | Security | skipped | — | 0 | |
| Release downloads | Security | ok | — | 0 | |
| Security posture | Security | ok | — | 0 | |
| Package registries | Security | skipped | — | 0 | no registry dependencies declared |
| Static analysis (opengrep) | Security | ok | opengrep 1.33.1; rules f1d2b562b414 | 9 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 0 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | 15ad976b7036 | prov-5+qual-2+sec-2 | 0% | 60 | 59 |
| 2026-11-14 | 15ad976b7036 | prov-4+qual-2+sec-2 | 0% | 60 | 59 |
Full text report
- Repository: https://github.com/asmuth/recommendify
- Commit:
15ad976b703695ecc4f24b08d3a7b86ef01180fe - Generated: 2026-11-14T14:52:02+00:00
- Scorer 0.1.0, scoring prov-5+qual-2+sec-2, report schema v2
Scores
| Pillar | Score | Signal | Confidence | Coverage |
|---|---|---|---|---|
| AI provenance (estimated AI-generated share) | 0 | none-detected | 65% | 100% |
| Code quality | 60 | weak | 90% | 100% |
| Security | 59 | 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 |
|---|---|---|
| 2012-01 | 1,492 | 0% |
| 2012-02 | 879 | 0% |
| 2012-03 | 124 | 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 weak: test-to-source ratio 0.80, no CI test run detected; 28% of function code in complex or long functions; 0% duplicated lines. Weakest area: lint.
| Area | Score |
|---|---|
| Complexity (lizard) | 44 |
| Duplication | 100 |
| Code smells (Opengrep) | 37 |
| Tests and CI | 70 |
| Documentation | 40 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 78; mean complexity 1.8, 90th percentile 2; 1 complex and 1 long functions
- Duplicated lines: 0.0% of 529 compared
- Tests: 687 test lines for 855 source lines (ratio 0.80); CI test commands: none detected; 35% of recent source commits also change tests
- Docs missing or thin: license, contributing, changelog
Most complex functions:
Security
Security posture is weak: 1 high-severity SAST findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 38 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
- Posture checks passed: none; missing: security policy, dependency updates, signed commits, lockfiles
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | opengrep/ruby.lang.security.model-attributes-attr-accessible: Checks for models that do not use attr_accessible. This means there is no limiting of which variables can be manipulated through mass assignment. For newer Rails applications, parameters should be allowlisted using strong parameters. For older Rails versions, they should be allowlisted using strong_ [confidence low] |
doc/example.rb:9 |
| medium | opengrep/c.lang.security.insecure-use-printf-fn: Avoid using user-controlled format strings passed into 'sprintf', 'printf' and 'vsprintf'. These functions put you at risk of buffer overflow vulnerabilities through the use of format string exploits. Instead, use 'snprintf' and 'vsnprintf'. [confidence low] |
ext/recommendify.c:49 |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] |
ext/recommendify.c:66 |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] |
ext/recommendify.c:70 |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] |
ext/recommendify.c:76 |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] |
ext/recommendify.c:129 |
| medium | opengrep/c.lang.security.insecure-use-strcat-fn: Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] |
ext/recommendify.c:154 |
| medium | opengrep/c.lang.security.insecure-use-strcat-fn: Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] |
ext/recommendify.c:155 |
| medium | opengrep/ruby.lang.security.dangerous-subshell: Detected non-static command inside .... If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. [confidence low] |
lib/recommendify/jaccard_input_matrix.rb:37 |
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: 855; test lines: 687
| Language | Lines |
|---|---|
| Ruby | 1,218 |
| C | 324 |