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
166 of your 263 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 18.05s · analysis 19.2s · 63.9 MB · GitHub API rate-limit (preflight)

near/nearcore

https://github.com/near/nearcore · scanned 2026-06-05 20:45 UTC (4 days, 12 hours ago) · 10 languages

830 raw signals (246 security + 584 graph) 11/13 scanners ran 62nd percentile · Rust · huge (>500K LoC) System graph score 60 (higher by 25)

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

Complete repo analysis

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

JSON
Combined
70.6
/100
Security checks
82
80 findings
System graph
60
100.0% cov · 205 findings
Critical
3
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 85.0 0.20 17.00
documentation_score 97.0 0.15 14.55
practices_score 90.0 0.15 13.50
code_quality 57.0 0.10 5.70
Overall 1.00 84.8
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 3 High 24 Medium 54 Low 143 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 80 System graph 205 Crowd 0 Layer: Software 49 Quality 175 Security 19 Cicd 17 Api 1 Frontend 2 Network 5 Hardware 17
Scan summary Quality grade A- (85/100). Dimensions: security 100, maintainability 60. 246 findings (76 security). 508,129 lines analyzed.

Showing 220 of 285 actionable findings. 538 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical Security checks quality Quality conf 1.00 ✓ Repobility [MINED013] Password In Url: https://user:password@host — leaks creds via logs, referrer, error messages.
Review and fix per the pattern semantics. See CWE-200 / A07:2021 for context.
tracing/docker-compose.yml:22
critical Security checks quality Quality conf 1.00 ✓ Repobility [MINED013] Password In Url: https://user:password@host — leaks creds via logs, referrer, error messages.
Review and fix per the pattern semantics. See CWE-200 / A07:2021 for context.
runtime/runtime-params-estimator/estimator-warehouse/src/zulip.rs:48
critical Security checks cicd CI/CD security conf 0.96 Compose service contains a literal secret environment value
Rotate the value if real. Move it to Docker Compose secrets, a platform secret manager, or an uncommitted environment file.
tracing/docker-compose.yml:2 CI/CD securitycontainers
low Security checks cicd CI/CD security conf 0.35 ✓ Repobility Workflow references repository secrets in a pull_request workflow
Fork pull_request runs do not receive normal repository secrets on GitHub Actions. Review this as a reliability/intent signal, not as direct fork-secret exfiltration. Raise severity only for pull_request_target or another trusted-context path that runs untrusted PR code with secrets.
.github/workflows/nayduck_ci.yml:48 CI/CD securityworkflow secretsGitHub Actions
high Security checks security auth conf 0.70 [AUC003] Object-level route lacks visible authorization: A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: ANY /debug/api/epoch_info/{epoch_id}.
Add ownership, tenant, relationship, or policy checks before reading or mutating the target object.
chain/jsonrpc/src/lib.rs:3028
high Security checks security auth conf 0.70 [AUC003] Object-level route lacks visible authorization: A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: ANY /debug/api/epoch_info_light/{epoch_id}.
Add ownership, tenant, relationship, or policy checks before reading or mutating the target object.
chain/jsonrpc/src/lib.rs:3029
high Security checks quality Quality conf 1.00 ✓ Repobility 3 occurrences [MINED034] Python Subprocess Shell True: subprocess(..., shell=True) enables command injection.
Review and fix per the pattern semantics. See CWE-78 / for context.
3 files, 3 locations
scripts/ft-benchmark-data-sender.py:94
scripts/remote_diff/utils.py:5
scripts/run-ft-benchmark.py:31
high Security checks software dependencies conf 0.90 ✓ Repobility 11 occurrences [MINED118] Dockerfile FROM `ubuntu:24.04` not pinned by digest: `FROM ubuntu:24.04` resolves the tag at build time. The registry CAN re-push a different image for the same tag, so every build is potentially different. Production images should pin to `image@sha256:...` for reproducibility + supply-chain integrity.
Replace with: `FROM ubuntu:24.04@sha256:<digest>`. Get the digest from `docker manifest inspect`. Re-pin via a scheduled bot (Renovate, Dependabot).
7 files, 11 locations
Dockerfile:2, 37 (2 hits)
docker/sandbox/Dockerfile:2, 8 (2 hits)
tools/debug-ui/Dockerfile:1, 15 (2 hits)
tracing/Dockerfile:2, 9 (2 hits)
.devcontainer/Dockerfile:1
.gitpod.Dockerfile:1
runtime/runtime-params-estimator/emu-cost/Dockerfile:2
high Security checks software dependencies conf 0.90 ✓ Repobility 2 occurrences [MINED119] Dockerfile `ADD https://s3-us-west-1.amazonaws.com/build.nearprotocol.com/nearcore/Linux-x86_64/${VERSION}/near-sandbox.tar.gz`: Dockerfile `ADD <url>` downloads a remote artifact into the image with no integrity check. If the host or DNS is compromised between layers — or if the URL serves a different file later — malicious content gets baked into the image.
Download the file in CI with a known checksum, vendor it into the repo, and COPY it during the build. Or use `RUN curl -sSL URL | sha256sum -c <(echo '<expected> -')` to verify.
lines 5, 11
docker/sandbox/Dockerfile:5, 11 (2 hits)
high Security checks software dependencies conf 0.90 ✓ Repobility [MINED134] Binary file `runtime/runtime-params-estimator/emu-cost/counter_plugin/libcounter.so` committed in source repo: `runtime/runtime-params-estimator/emu-cost/counter_plugin/libcounter.so` is a .so binary (16,536 bytes) committed to a repo that otherwise has 1590 source files. Trojan binaries inside otherwise-normal source repos are a known supply-chain attack: a compromised dependency or PR slips in a binary that gets executed by build scripts.
Audit the binary's provenance. If it's vendored library code, document it in a VENDORED.md. If it's a build artifact, add the extension to .gitignore and rebuild from source.
runtime/runtime-params-estimator/emu-cost/counter_plugin/libcounter.so:1
high Security checks software Resource exhaustion conf 1.00 [SEC035] Unbounded Resource Allocation — DoS risk: Allocating resources (buffers, recursion stack, large ranges) based on user input without an upper bound. Attackers send `size=10000000` to exhaust memory, or trigger expensive computation. CWE-770/400. Examples: CVE-2023-44487 (HTTP/2 Rapid Reset), countless YAML/XML billion-laughs variants.
Cap user-controlled sizes BEFORE allocation: size = min(int(request.args.get('n', 100)), MAX_SIZE) Set framework-level limits: Flask: app.config['MAX_CONTENT_LENGTH'] = 10 * 1024 * 1024 FastAPI: use middleware to enforce request size Django: DATA_UPLOAD_MAX_MEMORY_SIZE in settings.py …
runtime/runtime-params-estimator/src/estimator_params.rs:39
low Security checks security Injection conf 1.00 [SEC103] LDAP injection — non-constant search filter: User input concatenated into an LDAP search filter. Attackers inject `*)(uid=*` style payloads to bypass auth or enumerate accounts.
Escape with javax.naming.ldap.Rdn.escapeValue or equivalent. For python-ldap, use ldap.filter.escape_filter_chars. Better: use parameterized search APIs (Spring LdapTemplate filter encoders).
scripts/check_nightly.py:54
low Security checks security Injection conf 1.00 [SEC103] LDAP injection — non-constant search filter: User input concatenated into an LDAP search filter. Attackers inject `*)(uid=*` style payloads to bypass auth or enumerate accounts.
Escape with javax.naming.ldap.Rdn.escapeValue or equivalent. For python-ldap, use ldap.filter.escape_filter_chars. Better: use parameterized search APIs (Spring LdapTemplate filter encoders).
runtime/near-vm-runner/benchmarks/analyze_compilation_logs.py:38
high Security checks cicd CI/CD security conf 0.90 2 occurrences Database service has no persistent data volume
Mount the database data directory to a named Docker volume or managed persistent disk, and document backup and restore testing.
lines 2, 13
tracing/docker-compose.yml:2, 13 (2 hits)
CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.84 2 occurrences Database service publishes a host port
Use `expose` for service-to-service access, bind to 127.0.0.1 for local-only access, or protect the port with firewall rules.
lines 2, 13
tracing/docker-compose.yml:2, 13 (2 hits)
CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.92 3 occurrences Dockerfile pipes a remote script into a shell
Download the artifact, verify its checksum or signature, pin the version, and then execute it.
2 files, 3 locations
.devcontainer/Dockerfile:106, 121 (2 hits)
Dockerfile:24
CI/CD securitycontainers
low Security checks cicd CI/CD security conf 0.90 ✓ Repobility 39 occurrences GitHub Action is tag-pinned rather than SHA-pinned
[MINED115] Action `actions/checkout` pinned to mutable ref `@v2`: `uses: actions/checkout@v2` resolves at workflow-run time. Tags and branches can be re-pushed by the action owner; that made the tj-actions/changed-files compromise (2025) instantly affect ~23K repos. Pin to a 40-char commit SHA + lo…
11 files, 39 locations
.github/workflows/neard_release.yml:36, 43, 103, 110, 172, 179, 257 (14 hits)
.github/workflows/mac_m1_binary.yml:43, 50 (4 hits)
.github/workflows/neard_assertion_binary.yml:32, 39 (4 hits)
.github/workflows/book.yml:19, 32, 46 (3 hits)
.github/workflows/ci.yml:55, 94 (2 hits)
.github/workflows/master_fuzzer_binaries.yml:26 (2 hits)
.github/workflows/nayduck_ci.yml:31, 37 (2 hits)
.github/workflows/nayduck_ci_dev.yml:18 (2 hits)
CI/CD securitySupply chainGitHub Actions
high System graph hardware Supply chain conf 1.00 3 occurrences Dockerfile pipes a remote installer into a shell
Executing downloaded code during image build gives the remote endpoint build-time code execution. Prefer pinned packages or verify downloaded installers by checksum/signature.
lines 68, 105, 121
.devcontainer/Dockerfile:68, 105, 121 (3 hits)
containersRemote installer
high System graph security security conf 1.00 Insecure pattern 'exec_used' in chain/jsonrpc/openapi/openapi.json:4194
Found a known-risky pattern (exec_used). Review and replace if possible.
chain/jsonrpc/openapi/openapi.json:4194 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in chain/jsonrpc/openapi/openrpc.json:3098
Found a known-risky pattern (exec_used). Review and replace if possible.
chain/jsonrpc/openapi/openrpc.json:3098 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in runtime/runtime-params-estimator/src/main.rs:132
Found a known-risky pattern (exec_used). Review and replace if possible.
runtime/runtime-params-estimator/src/main.rs:132 Exec used
medium Security checks security auth conf 0.92 [AUC001] No Repobility access matrix policy found: The repository uses web/API frameworks but does not define .repobility/access.yml or equivalent authorization documentation.
Add .repobility/access.yml mapping routes to anonymous, authenticated, owner, admin, and super_admin. Keep business-specific rules in the repo so CI can enforce them.
high Security checks security auth conf 0.74 [AUC002] Low visible authorization coverage in route inventory: Only 24.3% of discovered routes show nearby authentication, authorization, middleware, or public-route evidence.
Review the access matrix and add explicit framework auth declarations or policy-file exceptions for intentionally public routes.
medium Security checks software dependencies conf 0.90 ✓ Repobility 25 occurrences [MINED124] requirements.txt: `PyGithub` has no version pin: Unpinned pip requirement means every fresh install may resolve a different version. Newer releases can introduce malicious code (typosquats, account compromises). Reproducible installs need exact pins.
Replace `PyGithub` with `PyGithub==<version>` and manage upgrades through PRs / Dependabot.
2 files, 25 locations
pytest/requirements.txt:1, 2, 3, 4, 5, 6, 10, 11, +14 more (22 hits)
pytest/tests/mocknet/helpers/requirements.txt:1, 2, 3 (3 hits)
low Security checks security Injection conf 0.50 3 occurrences [SEC005] Command Injection Risk: Unsafe shell execution or eval of user input.
Use subprocess with shell=False and a list of args. Never eval user input.
3 files, 3 locations
scripts/ft-benchmark-data-sender.py:94
scripts/remote_diff/utils.py:5
scripts/run-ft-benchmark.py:31
low Security checks quality Error handling conf 0.55 ✓ Repobility 4 occurrences Broad exception handler needs review
This handler catches Exception/BaseException. It is actionable when it swallows errors without logging, re-raising, or returning a structured error. Handlers that intentionally convert exceptions into typed error results should not be treated as high risk.
3 files, 4 locations
scripts/merge_queue_health.py:170, 255 (2 hits)
pytest/lib/cluster.py:108
pytest/lib/mocknet_helpers.py:85
Error handlingquality
medium Security checks cicd CI/CD security conf 0.88 2 occurrences Database service has no healthcheck
Add a database-native healthcheck such as pg_isready, mysqladmin ping, redis-cli ping, or the vendor's readiness command.
lines 2, 13
tracing/docker-compose.yml:2, 13 (2 hits)
CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.82 5 occurrences Docker final stage has no non-root USER
Add a non-root USER in the final runtime stage after files and permissions are prepared.
5 files, 5 locations
Dockerfile:37
docker/sandbox/Dockerfile:17
runtime/runtime-params-estimator/emu-cost/Dockerfile:2
tools/debug-ui/Dockerfile:15
tracing/Dockerfile:10
CI/CD securitycontainers
medium Security checks cicd CI/CD security conf 0.84 2 occurrences Dockerfile ADD downloads remote content
Use curl/wget with a pinned URL, verify checksum or signature, and prefer COPY for local files.
lines 5, 11
docker/sandbox/Dockerfile:5, 11 (2 hits)
CI/CD securitycontainers
medium Security checks cicd CI/CD security conf 0.76 Dockerfile copies broad context with incomplete .dockerignore
Tighten .dockerignore or replace COPY . with explicit COPY statements.
Dockerfile:18 CI/CD securitycontainers
high Security checks quality Quality conf 0.82 Parallel implementation file sits beside a canonical file
Merge the intended change into the canonical file, update tests/imports, and delete the parallel implementation if it is not the active entry point.
core/store/src/trie/trie_storage_update.rs:1
high Security checks quality Quality conf 0.82 Parallel implementation file sits beside a canonical file
Merge the intended change into the canonical file, update tests/imports, and delete the parallel implementation if it is not the active entry point.
chain/chain/src/chain_update.rs:1
medium Security checks quality Quality conf 0.78 Suspicious implementation file appears unreferenced
Confirm whether this file is reachable. If not, delete it; if yes, wire it through explicit imports, routes, or entry points and add a test that proves the path executes.
core/store/src/trie/trie_storage_update.rs:1
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — chain/jsonrpc/res/congestion_control.js:107
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — chain/jsonrpc/res/last_blocks.js:262
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — tools/debug-ui/src/entity_debug/EntityDataRootView.tsx:44
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — tools/debug-ui/src/entity_debug/EntityDataValueView.tsx:40
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — tools/debug-ui/src/entity_debug/EntityQueryComposer.tsx:51
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — tools/debug-ui/src/entity_debug/fetcher.tsx:17
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: download-${TARGETARCH}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker/sandbox/Dockerfile:17 containersPinned dependencies
medium System graph hardware Supply chain conf 1.00 2 occurrences Dockerfile ADD downloads remote content without checksum
Remote build inputs can change or be replaced upstream. Use Dockerfile ADD --checksum or download with an explicit digest/signature verification step.
lines 5, 11
docker/sandbox/Dockerfile:5, 11 (2 hits)
containersChecksum
medium System graph hardware Security conf 1.00 Dockerfile runs as root: .devcontainer/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: docker/sandbox/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: runtime/runtime-params-estimator/emu-cost/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: tools/debug-ui/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: tracing/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 2 occurrences Frontend route `floating_chunks` has no Link/navigate to it — tools/debug-ui/src/ChainAndChunkInfoView.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
2 occurrences
repo-level (2 hits)
Orphan pageWiring
medium System graph quality Integrity conf 1.00 8 occurrences Frontend route `last_blocks` has no Link/navigate to it — tools/debug-ui/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
8 occurrences
repo-level (8 hits)
Orphan pageWiring
medium System graph quality Integrity conf 1.00 4 occurrences Frontend route `peer_storage` has no Link/navigate to it — tools/debug-ui/src/NetworkInfoView.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
4 occurrences
repo-level (4 hits)
Orphan pageWiring
medium System graph quality Integrity conf 1.00 2 occurrences Frontend route `validators` has no Link/navigate to it — tools/debug-ui/src/EpochInfoView.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
2 occurrences
repo-level (2 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 32 occurrences GitHub Action is tag-pinned rather than SHA-pinned
google-github-actions/auth@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
11 files, 32 locations
.github/workflows/neard_release.yml:48, 115, 154, 184, 190, 195, 236 (9 hits)
.github/workflows/ci.yml:64, 129, 181, 253, 283, 361, 391, 484 (8 hits)
.github/workflows/issue-metrics.yml:32, 38 (2 hits)
.github/workflows/mac_m1_binary.yml:33 (2 hits)
.github/workflows/master_fuzzer_binaries.yml:32, 55 (2 hits)
.github/workflows/neard_assertion_binary.yml:25 (2 hits)
.github/workflows/neard_custom_binary.yml:37 (2 hits)
.github/workflows/neard_nightly_binary.yml:22 (2 hits)
CI/CD securitySupply chainGitHub Actions
medium System graph cicd CI/CD security conf 1.00 7 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
7 files, 7 locations
.github/workflows/book.yml
.github/workflows/mac_m1_binary.yml
.github/workflows/near_crates_publish.yml
.github/workflows/neard_assertion_binary.yml
.github/workflows/neard_custom_binary.yml
.github/workflows/neard_nightly_binary.yml
.github/workflows/neard_release.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in chain/jsonrpc/src/lib.rs:192
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
chain/jsonrpc/src/lib.rs:192 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in chain/rosetta-rpc/src/config.rs:17
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
chain/rosetta-rpc/src/config.rs:17 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in chain/rosetta-rpc/src/lib.rs:1063
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
chain/rosetta-rpc/src/lib.rs:1063 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in scripts/ft-benchmark-data-sender.py:95
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
scripts/ft-benchmark-data-sender.py:95 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in scripts/remote_diff/utils.py:13
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
scripts/remote_diff/utils.py:13 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in scripts/run-ft-benchmark.py:31
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
scripts/run-ft-benchmark.py:31 Subprocess shell true
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — debug_scripts/estimate_epoch_start_time.py:23
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — debug_scripts/request_chain_info.py:63
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pytest/lib/branches.py:34
`subprocess.check_output(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pytest/lib/cluster.py:636
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pytest/lib/network.py:9
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pytest/lib/utils.py:143
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pytest/tools/mirror/mirror_utils.py:174
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pytest/tools/prober/prober_split.py:136
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/check_import_blocks.py:150
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/ft-benchmark-data-sender.py:31
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/nayduck.py:89
`subprocess.check_output(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/nayduck_v2.py:306
`subprocess.check_output(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/remote_diff/utils.py:5
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/run-ft-benchmark.py:31
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/track_release_commits.py:105
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — tools/debug-ui/scripts/compare_tries.py:17
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph network Security conf 1.00 Privileged port 14 in use
Port 14 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
benchmarks/sharded-bm/bench.sh Ports
medium System graph network Security conf 1.00 Privileged port 15 in use
Port 15 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/lychee_lints.yml Ports
medium System graph network Security conf 1.00 Privileged port 17 in use
Port 17 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/lychee_lints.yml Ports
medium System graph network Security conf 1.00 Privileged port 24 in use
Port 24 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
benchmarks/sharded-bm/bench.sh Ports
medium System graph network Security conf 1.00 Privileged port 49 in use
Port 49 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
benchmarks/sharded-bm/bench.sh Ports
low Security checks cicd CI/CD security conf 0.72 .dockerignore misses sensitive defaults
Add missing patterns such as .env, .git, private keys, certificates, dependency folders, and local databases.
.dockerignore CI/CD securitycontainers
low Security checks security auth conf 0.76 [AUC005] No authorization-focused tests detected: No test files with common authorization, ownership, 403, admin, or super_admin assertions were found.
Add regression tests for anonymous denial, cross-user object denial, admin role limits, and super_admin-only behavior.
low Security checks software Race condition conf 1.00 [SEC124] TOCTOU file access (os.access then open): Check-then-use file pattern (access/exists then open) lets an attacker swap the file between check and use (symlink attack). `mktemp` is deprecated for the same reason.
Use `os.open(path, os.O_CREAT | os.O_EXCL | os.O_WRONLY)` for atomic create-only. Use `tempfile.NamedTemporaryFile()` (not `mktemp`). For locking, use `fcntl.flock`.
scripts/run-ft-benchmark.py:11
high Security checks cicd CI/CD security conf 0.56 2 occurrences Compose service does not declare a runtime user
Set a non-root `user:` in Compose or ensure the final image stage has a non-root USER directive.
lines 25, 31
tracing/docker-compose.yml:25, 31 (2 hits)
CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.62 2 occurrences Compose service lacks no-new-privileges hardening
Add `security_opt: ["no-new-privileges:true"]` unless the service has a documented need for privilege escalation.
lines 25, 31
tracing/docker-compose.yml:25, 31 (2 hits)
CI/CD securitycontainers
low Security checks cicd CI/CD security conf 0.72 3 occurrences Dockerfile installs recommended OS packages
Add `--no-install-recommends` and explicitly list only packages the image needs.
2 files, 3 locations
Dockerfile:5, 41 (2 hits)
runtime/runtime-params-estimator/emu-cost/Dockerfile:9
CI/CD securitycontainers
low Security checks cicd CI/CD security conf 0.74 Dockerfile leaves apt package indexes in the image layer
End the apt install layer with `rm -rf /var/lib/apt/lists/*`.
runtime/runtime-params-estimator/emu-cost/Dockerfile:9 CI/CD securitycontainers
low Security checks quality Quality conf 0.60 30 occurrences Duplicated implementation block across source files
Duplicate implementation blocks are maintenance debt. Keep them visible, but they are not a high-severity defect unless the duplicated logic is security-sensitive or drifting.
12 files, 16 locations
chain/jsonrpc-primitives/src/types/query.rs:14, 35 (2 hits)
chain/jsonrpc-primitives/src/types/view_account.rs:11, 13 (2 hits)
chain/rosetta-rpc/src/adapters/validated_operations/transfer_to_gas_key.rs:11, 19 (2 hits)
chain/rosetta-rpc/src/adapters/validated_operations/withdraw_from_gas_key.rs:11, 19 (2 hits)
chain/jsonrpc-primitives/src/types/light_client.rs:33
chain/jsonrpc-primitives/src/types/view_access_key.rs:12
chain/jsonrpc-primitives/src/types/view_access_key_list.rs:11
chain/jsonrpc-primitives/src/types/view_code.rs:11
duplicationquality
high Security checks quality Quality conf 0.62 Source file name looks like an AI patch artifact
Rename it to the domain concept it implements or merge it into the existing module it was meant to change.
core/store/src/trie/mem/memtrie_update.rs:1
low System graph quality Maintenance conf 1.00 431 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: debian:bullseye-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
tracing/Dockerfile:9 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: docker.io/rust:1.86.0
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
runtime/runtime-params-estimator/emu-cost/Dockerfile:2 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: nginx:1.25.4-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
tools/debug-ui/Dockerfile:15 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:19-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
tools/debug-ui/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: rust:1.86.0-bullseye
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
tracing/Dockerfile:2 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: ubuntu:22.04
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 2, 37
Dockerfile:2, 37 (2 hits)
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 3 occurrences Docker base image is tag-pinned but not digest-pinned: ubuntu:24.04
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
2 files, 3 locations
docker/sandbox/Dockerfile:2, 8 (2 hits)
.devcontainer/Dockerfile:1
containersPinned dependencies
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/adversarial/fork_sync.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/adversarial/gc_rollback.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/adversarial/malicious_chain.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/adversarial/start_from_genesis.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/contracts/gibberish.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/mocknet/stop.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sandbox/fast_forward.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sandbox/fast_forward_epoch_boundary.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sandbox/patch_state.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sanity/garbage_collection_archival.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sanity/garbage_collection_intense.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sanity/handshake_tie_resolution.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sanity/one_val.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sanity/rpc_tx_forwarding.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sanity/rpc_tx_submission.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sanity/staking_repro1.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sanity/staking_repro2.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sanity/state_sync_routed.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sanity/switch_node_key.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sanity/transactions.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: pytest/tests/sanity/validator_switch.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: runtime/runtime-params-estimator/emu-cost/data_builder.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: scripts/state/mega-migrate.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: scripts/state/split-genesis.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tools/debug-ui/src/actors/constants.tsx
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tools/debug-ui/src/entity_debug/view_options.tsx
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tools/debug-ui/src/index.tsx
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tools/debug-ui/src/react-app-env.d.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph quality Integrity conf 1.00 17 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/nayduck_v2.py:api_get_runs, scripts/nayduck_v2.py:api_get_run This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
17 occurrences
repo-level (17 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: pytest/lib/account.py:json_rpc, pytest/lib/cluster.py:json_rpc, pytest/lib/cluster.py:json_rpc This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're sepa…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `compute_v1` in pytest/lib/cluster.py:28
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `do_make_backup` in pytest/tests/mocknet/helpers/neard_runner.py:58
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `nayduck_v2` in scripts/nayduck_v2.py:49
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `neard_runner_make_backup` in pytest/tests/mocknet/mirror.py:549
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `neard_runner_make_backup` in pytest/tests/mocknet/node_handle.py:195
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: api_cancel_run
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/nayduck_v2.py:395
low System graph software Dead code conf 1.00 Possibly dead Python function: api_retry_run
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/nayduck_v2.py:400
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_build
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/nayduck_v2.py:624
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_cancel
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/nayduck_v2.py:668
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_history
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/nayduck_v2.py:605
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_logs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/nayduck_v2.py:595
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_nightly
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/nayduck_v2.py:613
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_retry
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/nayduck_v2.py:672
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_run
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/nayduck_v2.py:579
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_runs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/nayduck_v2.py:571
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_schedule
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/nayduck_v2.py:632
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_test
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/nayduck_v2.py:587
low System graph software Dead code conf 1.00 Possibly dead Python function: valid_timezone
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
debug_scripts/estimate_epoch_start_time.py:86
low System graph software Dead code conf 1.00 Possibly dead Python function: valid_voting_datetime
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
debug_scripts/estimate_epoch_start_time.py:171
low System graph quality Integrity conf 1.00 Stub function `check_fork` (body is just `pass`/`return`) — pytest/tools/mirror/offline_test.py:64
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Complexity conf 1.00 Very large file: benchmarks/transactions-generator/src/lib.rs (1544 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/chain/src/chain.rs (4237 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/chain/src/doomslug.rs (1295 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/chain/src/garbage_collection.rs (1175 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/chain/src/resharding/flat_storage_resharder.rs (1527 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/chain/src/runtime/mod.rs (1878 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/chain/src/runtime/tests.rs (2550 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/chain/src/spice/chunk_validation.rs (1541 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/chain/src/spice/tests/core.rs (1723 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/chain/src/store/mod.rs (2513 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/chunks/src/shards_manager_actor.rs (3793 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/client/src/client.rs (2793 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/client/src/client_actor.rs (2149 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/client/src/spice/chunk_executor_actor.rs (1363 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/client/src/spice/data_distributor_actor.rs (1246 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/client/src/spice/tests/data_distributor_actor.rs (2398 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/client/src/view_client_actor.rs (1918 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/epoch-manager/src/lib.rs (1945 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/epoch-manager/src/tests/mod.rs (3681 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/epoch-manager/src/validator_selection.rs (1352 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/jsonrpc/openapi/src/openrpc.rs (1437 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/jsonrpc/src/lib.rs (3162 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/network/src/network_protocol/mod.rs (1554 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/network/src/peer/peer_actor.rs (1699 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/network/src/peer_manager/network_state/mod.rs (1523 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/network/src/peer_manager/peer_manager_actor.rs (1731 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/network/src/peer_manager/tests/routing.rs (1413 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/rosetta-rpc/src/adapters/mod.rs (1588 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: chain/rosetta-rpc/src/models.rs (1473 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/chain-configs/src/genesis_config.rs (1289 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/crypto/src/signature.rs (1768 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/primitives/src/block_header.rs (1753 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/primitives/src/errors.rs (1608 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/primitives/src/receipt.rs (1424 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/primitives/src/sharding.rs (1767 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/primitives/src/trie_key.rs (1347 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/primitives/src/types.rs (1429 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/primitives/src/views.rs (3115 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/store/src/flat/storage.rs (1272 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/store/src/trie/mem/memtrie_update.rs (1282 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/store/src/trie/mod.rs (2436 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/store/src/trie/split.rs (1419 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/store/src/trie/state_parts.rs (1202 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: integration-tests/src/tests/client/process_blocks.rs (3659 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: integration-tests/src/tests/standard_cases/mod.rs (1989 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: nearcore/src/config.rs (2289 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: pytest/tests/mocknet/helpers/neard_runner.py (1615 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/near-test-contracts/estimator-contract/src/lib.rs (1540 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/near-test-contracts/test-contract-rs/src/lib.rs (2149 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/near-vm-runner/src/cache.rs (1954 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/near-vm-runner/src/logic/logic.rs (4517 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/near-vm-runner/src/logic/tests/bls12381.rs (1793 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/near-vm-runner/src/wasmtime_runner/logic.rs (4877 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/near-vm-runner/src/wasmtime_runner/mod.rs (1292 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/near-vm/compiler-singlepass/src/codegen_x64.rs (8128 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/near-vm/compiler-singlepass/src/emitter_x64.rs (1397 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/near-vm/test-api/src/sys/externals/function.rs (1578 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/runtime-params-estimator/src/lib.rs (1665 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/runtime/src/actions.rs (2054 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/runtime/src/lib.rs (3237 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/runtime/src/tests/apply.rs (4225 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/runtime/src/verifier.rs (2736 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: runtime/runtime/tests/test_async_calls.rs (1462 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test-loop-tests/src/tests/cloud_archival.rs (1274 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test-loop-tests/src/tests/deterministic_account_id.rs (1403 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test-loop-tests/src/tests/receipt_to_tx/hint.rs (1477 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test-loop-tests/src/tests/resharding_v3.rs (1992 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test-loop-tests/src/tests/sharded_rpc.rs (1672 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test-loop-tests/src/utils/resharding.rs (1618 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tools/fork-network/src/cli.rs (1665 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tools/mirror/src/lib.rs (2439 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tools/state-viewer/src/commands.rs (1642 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/5a61929d-0913-4b71-83d9-67fdb6a96315/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5a61929d-0913-4b71-83d9-67fdb6a96315/

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.