Leaderboard github.com
rendrjs/rendr
Render your Backbone.js apps on the client and the server, using Node.js.
AI provenance
0%
none-detected
- Confidence
- 65%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
74/100
adequate
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
56/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 pace0
- Coding-style index (1.0+ means possible)0.31
Lines added per month all AI-attributed share
- 2012-100 · 0% AI
- 2012-111,369 · 0% AI
- 2012-120 · 0% AI
- 2013-010 · 0% AI
- 2013-020 · 0% AI
- 2013-030 · 0% AI
- 2013-044,893 · 0% AI
- 2013-05589 · 0% AI
- 2013-06738 · 0% AI
- 2013-07221 · 0% AI
- 2013-08107 · 0% AI
- 2013-09257 · 0% AI
- 2013-102,410 · 0% AI
- 2013-114,617 · 0% AI
- 2013-121,912 · 0% AI
- 2014-01652 · 0% AI
- 2014-021,338 · 0% AI
- 2014-03103 · 0% AI
- 2014-0465 · 0% AI
- 2014-0532 · 0% AI
- 2014-06213 · 0% AI
- 2014-0718 · 0% AI
- 2014-08551 · 0% AI
- 2014-09638 · 0% AI
- 2014-10533 · 0% AI
- 2014-11341 · 0% AI
- 2014-12100 · 0% AI
- 2015-01275 · 0% AI
- 2015-0279 · 0% AI
- 2015-03226 · 0% AI
- 2015-04300 · 0% AI
- 2015-05410 · 0% AI
- 2015-06131 · 0% AI
- 2015-075 · 0% AI
- 2015-090 · 0% AI
- 2015-1053 · 0% AI
- 2015-111 · 0% AI
- 2016-0325 · 0% AI
- 2016-0537 · 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
- 979
- effective_loc
- 23,239
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 4,111
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 547
- measured_loc
- 19,128
- median_loc_per_hour
- 62.30
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 2,188
- pre_ai_era_bursts
- 1
- pre_ai_era_measured_loc
- 19,128
- work_units
- 334
Release velocityok
- flagged_releases
- 0
- max_loc_per_day
- 1,587.30
- releases
- 57
Coding styleok1 item
- count:assistant_voice
- 0
- count:emoji_in_code
- 0
- count:narrated_steps
- 1
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 0
- files:narrated_steps
- 1
- files:placeholder
- 0
- index
- 0.31
- lines_scanned
- 3,215
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0.31
- per_kloc:placeholder
- 0
Code quality
74 adequate
Code quality is adequate: test-to-source ratio 1.79, no CI test run detected; 0% of function code in complex or long functions; 0% duplicated lines. Weakest area: process.
How the score is built
- Complexity100
- Duplication100
- Lint and smells54
- Tests and CI70
- Documentation85
- Type safetynot measured
- Review process10
Evidence by analyzer
Complexity (lizard)ok
- complex_functions
- 0
- function_nloc
- 1,993
- functions
- 274
- long_functions
- 0
- many_param_functions
- 0
- mean_ccn
- 2.18
- p90_ccn
- 4
- risky_nloc_share
- 0.0%
Duplication (jscpd)ok
- compared_lines
- 1,950
- duplicated_lines
- 0
- duplicated_share
- 0.0%
- files
- 23
Lintok
- category:best-practice
- 7
- category:correctness
- 1
- findings
- 8
- scanned_lines
- 3,215
- weighted_findings
- 8
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
- 163
- cochange_share
- 49.1%
- source_lines
- 3,215
- test_lines
- 5,749
- test_ratio
- 1.79
Documentationok3 items
- README.md
README.md - LICENSE
LICENSE - HISTORY.md
HISTORY.md
- check:changelog
- yes
- check:contributing
- no
- check:license
- yes
- check:readme
- yes
- readme_lines
- 231
Type safetyskipped
Security
56 weak
Security posture is weak: 2 high-severity SAST findings. Weakest area: posture.
How the score is built
- Secrets82
- Static analysis (SAST)66
- Vulnerable dependenciesnot measured
- CI workflowsnot measured
- Security posture0
- OpenSSF Scorecard25
Evidence by analyzer
OpenSSF Scorecardok9 items
- Scorecard Maintained: 0/10 (0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0)
- Scorecard Code-Review: 2/10 (Found 7/24 approved changesets -- score normalized to 2)
- Scorecard Binary-Artifacts: 10/10 (no binaries found in the repo)
- Scorecard CII-Best-Practices: 0/10 (no effort to earn an OpenSSF best practices badge detected)
- Scorecard Security-Policy: 0/10 (security policy file not detected)
- Scorecard License: 10/10 (license file detected)
- Scorecard Fuzzing: 0/10 (project is not fuzzed)
- Scorecard Branch-Protection: 0/10 (branch protection not enabled on development/release branches)
- Scorecard SAST: 0/10 (SAST tool is not run on all commits -- score normalized to 0)
- aggregate
- 2.30
- check:Binary-Artifacts
- yes
- check:Branch-Protection
- no
- check:CII-Best-Practices
- no
- check:Code-Review
- yes
- check:Fuzzing
- no
- check:License
- yes
- check:Maintained
- no
- check:SAST
- no
- check:Security-Policy
- no
Package registriesok
- checked
- 20
- declared
- 20
- lookup_errors
- 0
- missing
- 0
- recent
- 0
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 5
- secrets_nonprod
- 1
Static analysis (opengrep)ok
- findings
- 13
- findings_high
- 2
- findings_low
- 2
- findings_medium
- 9
- parse_errors
- 0
- scanned_lines
- 3,215
- weighted_findings
- 3.88
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok1 item
- package.json has no lockfile alongside it (unpinned dependencies)
package.json
- 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
2 high17 medium8 low
27 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| high | opengrep/javascript.express.security.audit.remote-property-injection |
shared/base/view.js:567 | Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype. Use literal values for object properties. [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.express.security.audit.remote-property-injection |
shared/fetcher.js:98 | Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype. Use literal values for object properties. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.best-practice.lazy-load-module |
server/data_adapter/rest_adapter.js:22 | Lazy loading can complicate code bundling if care is not taken, also `require`s are run synchronously by Node.js. If they are called from within a function, it may block other requests from being handled at a more critical time. The... | Lint |
| medium | opengrep/javascript.lang.best-practice.lazy-load-module |
server/middleware/index.js:18 | Lazy loading can complicate code bundling if care is not taken, also `require`s are run synchronously by Node.js. If they are called from within a function, it may block other requests from being handled at a more critical time. The... | Lint |
| medium | opengrep/javascript.lang.best-practice.lazy-load-module |
shared/app.js:100 | Lazy loading can complicate code bundling if care is not taken, also `require`s are run synchronously by Node.js. If they are called from within a function, it may block other requests from being handled at a more critical time. The... | Lint |
| medium | opengrep/javascript.lang.best-practice.lazy-load-module |
shared/app.js:131 | Lazy loading can complicate code bundling if care is not taken, also `require`s are run synchronously by Node.js. If they are called from within a function, it may block other requests from being handled at a more critical time. The... | Lint |
| medium | opengrep/javascript.lang.best-practice.lazy-load-module |
shared/app.js:97 | Lazy loading can complicate code bundling if care is not taken, also `require`s are run synchronously by Node.js. If they are called from within a function, it may block other requests from being handled at a more critical time. The... | Lint |
| medium | opengrep/javascript.lang.best-practice.lazy-load-module |
shared/base/router.js:110 | Lazy loading can complicate code bundling if care is not taken, also `require`s are run synchronously by Node.js. If they are called from within a function, it may block other requests from being handled at a more critical time. The... | Lint |
| medium | opengrep/javascript.lang.best-practice.lazy-load-module |
shared/base/router.js:81 | Lazy loading can complicate code bundling if care is not taken, also `require`s are run synchronously by Node.js. If they are called from within a function, it may block other requests from being handled at a more critical time. The... | Lint |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
shared/base/view.js:173 | JSON stringify does not produce a stable key ordering, and should not be relied on for producing object keys. Consider using json-stable-stringify instead. | Lint |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
client/app_view.js:33 | JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-require |
server/middleware/index.js:18 | Detected the use of require(variable). Calling require with a non-literal argument might allow an attacker to load and run arbitrary code, or access arbitrary files. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-require |
server/middleware/initApp.js:14 | Detected the use of require(variable). Calling require with a non-literal argument might allow an attacker to load and run arbitrary code, or access arbitrary files. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-require |
shared/app.js:100 | Detected the use of require(variable). Calling require with a non-literal argument might allow an attacker to load and run arbitrary code, or access arbitrary files. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-require |
shared/app.js:97 | Detected the use of require(variable). Calling require with a non-literal argument might allow an attacker to load and run arbitrary code, or access arbitrary files. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-require |
shared/base/router.js:81 | Detected the use of require(variable). Calling require with a non-literal argument might allow an attacker to load and run arbitrary code, or access arbitrary files. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
shared/base/view.js:212 | JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-require |
shared/base/view.js:450 | Detected the use of require(variable). Calling require with a non-literal argument might allow an attacker to load and run arbitrary code, or access arbitrary files. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-require |
shared/base/view.js:453 | Detected the use of require(variable). Calling require with a non-literal argument might allow an attacker to load and run arbitrary code, or access arbitrary files. [confidence low] | Static analysis (opengrep) |
| low | gitleaks/generic-api-key |
Gruntfile.js:59 | Possible generic-api-key secret in history (commit 866574fd1c); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | opengrep/javascript.browser.security.js-open-redirect-from-function |
client/router.js:229 | The application accepts potentially user-controlled input `path` which can control the location of the current window context. This can lead two types of vulnerabilities open-redirection and Cross-Site-Scripting (XSS) with JavaScript... | Static analysis (opengrep) |
| low | gitleaks/generic-api-key |
config/environments/development.coffee:10 | Possible generic-api-key secret in history (commit e6662a5d9a); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
config/environments/environments.coffee:10 | Possible generic-api-key secret in history (commit 1e8671e099); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
config/environments/production.coffee:11 | Possible generic-api-key secret in history (commit 1e8671e099); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
config/environments/test.coffee:10 | Possible generic-api-key secret in history (commit e6662a5d9a); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
examples/02_middleware/server/middleware/fetchDataForApp.js:14 | Possible generic-api-key secret in history (commit cba7ea6030); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | opengrep/javascript.express.security.audit.express-check-csurf-middleware-usage |
server/server.js:40 | A CSRF middleware was not detected in your express application. Ensure you are either using one such as `csurf` or `csrf` (see rule references) and/or you are properly doing CSRF validation in your routes with a token or cookies.... | 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 | ok | prov-4 | 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 | 8 | |
| 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 | ok | — | 0 | |
| Static analysis (opengrep) | Security | ok | opengrep 1.33.1; rules f1d2b562b414 | 13 | |
| OpenSSF Scorecard | Security | ok | scorecard v5.6.0 | 0 | |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 6 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | 48560e1ca1ad | prov-5+qual-2+sec-2 | 0% | 74 | 56 |
| 2026-11-14 | 48560e1ca1ad | prov-4+qual-2+sec-2 | 0% | 74 | 56 |
Full text report
- Repository: https://github.com/rendrjs/rendr
- Commit:
48560e1ca1ad72c94c9c68fb9cfba3259163536e - Generated: 2026-11-14T14:52:07+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 | 74 | adequate | 90% | 100% |
| Security | 56 | 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%
-
Stylometry index: 0.31 per 1,000 lines (narrated steps 1, placeholders 0, assistant phrasing 0, emoji 0). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2014-12 | 100 | 0% |
| 2015-01 | 275 | 0% |
| 2015-02 | 79 | 0% |
| 2015-03 | 226 | 0% |
| 2015-04 | 300 | 0% |
| 2015-05 | 410 | 0% |
| 2015-06 | 131 | 0% |
| 2015-07 | 5 | 0% |
| 2015-10 | 53 | 0% |
| 2015-11 | 1 | 0% |
| 2016-03 | 25 | 0% |
| 2016-05 | 37 | 0% |
Evidence
- step-by-step narration comment: // First, see if we have stored the model or collection. (shared/fetch)
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.79, no CI test run detected; 0% of function code in complex or long functions; 0% duplicated lines. Weakest area: process.
| Area | Score |
|---|---|
| Complexity (lizard) | 100 |
| Duplication | 100 |
| Code smells (Opengrep) | 54 |
| Tests and CI | 70 |
| Documentation | 85 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | 10 |
- Functions: 274; mean complexity 2.2, 90th percentile 4; 0 complex and 0 long functions
- Duplicated lines: 0.0% of 1,950 compared
- Tests: 5,749 test lines for 3,215 source lines (ratio 1.79); CI test commands: none detected; 49% of recent source commits also change tests
- Docs missing or thin: contributing
Security
Security posture is weak: 2 high-severity SAST findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 82 |
| Static analysis (Opengrep) | 66 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | 25 |
- Posture checks passed: none; missing: security policy, dependency updates, signed commits, lockfiles
- OpenSSF Scorecard aggregate: 2.3/10 (published 2026-11-02)
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | opengrep/javascript.express.security.audit.remote-property-injection: Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype. Use literal values for object properties. [confidence low] |
shared/base/view.js:567 |
| high | opengrep/javascript.express.security.audit.remote-property-injection: Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype. Use literal values for object properties. [confidence low] |
shared/fetcher.js:98 |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html: JQuery's html function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider text instead. Otherwise, use a function that escapes HTML such as edX's HtmlUtils.setHtml(). [confidence low] |
client/app_view.js:33 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-require: Detected the use of require(variable). Calling require with a non-literal argument might allow an attacker to load and run arbitrary code, or access arbitrary files. [confidence low] |
server/middleware/index.js:18 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-require: Detected the use of require(variable). Calling require with a non-literal argument might allow an attacker to load and run arbitrary code, or access arbitrary files. [confidence low] |
server/middleware/initApp.js:14 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-require: Detected the use of require(variable). Calling require with a non-literal argument might allow an attacker to load and run arbitrary code, or access arbitrary files. [confidence low] |
shared/app.js:97 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-require: Detected the use of require(variable). Calling require with a non-literal argument might allow an attacker to load and run arbitrary code, or access arbitrary files. [confidence low] |
shared/app.js:100 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-require: Detected the use of require(variable). Calling require with a non-literal argument might allow an attacker to load and run arbitrary code, or access arbitrary files. [confidence low] |
shared/base/router.js:81 |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html: JQuery's html function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider text instead. Otherwise, use a function that escapes HTML such as edX's HtmlUtils.setHtml(). [confidence low] |
shared/base/view.js:212 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-require: Detected the use of require(variable). Calling require with a non-literal argument might allow an attacker to load and run arbitrary code, or access arbitrary files. [confidence low] |
shared/base/view.js:450 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-require: Detected the use of require(variable). Calling require with a non-literal argument might allow an attacker to load and run arbitrary code, or access arbitrary files. [confidence low] |
shared/base/view.js:453 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit cba7ea6030); removed from the current tree but still retrievable |
examples/02_middleware/server/middleware/fetchDataForApp.js:14 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 866574fd1c); removed from the current tree but still retrievable |
Gruntfile.js:59 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit e6662a5d9a); removed from the current tree but still retrievable |
config/environments/development.coffee:10 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit e6662a5d9a); removed from the current tree but still retrievable |
config/environments/test.coffee:10 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 1e8671e099); removed from the current tree but still retrievable |
config/environments/production.coffee:11 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 1e8671e099); removed from the current tree but still retrievable |
config/environments/environments.coffee:10 |
| low | opengrep/javascript.browser.security.js-open-redirect-from-function: The application accepts potentially user-controlled input path which can control the location of the current window context. This can lead two types of vulnerabilities open-redirection and Cross-Site-Scripting (XSS) with JavaScript URIs. It is recommended to validate user-controllable input before [confidence low] |
client/router.js:229 |
| low | opengrep/javascript.express.security.audit.express-check-csurf-middleware-usage: A CSRF middleware was not detected in your express application. Ensure you are either using one such as csurf or csrf (see rule references) and/or you are properly doing CSRF validation in your routes with a token or cookies. [confidence low] |
server/server.js:40 |
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: 3,215; test lines: 5,749
| Language | Lines |
|---|---|
| JavaScript | 8,964 |