← Scan another repo

github.com/mattn/go-sqlite3

@ f9fc7aaf8779

Submitted 8/4/2026, 1:45:37 AM · Status: ok

Risk grade
F
97 / 100
Findings
65
0 critical7 high6 medium1 low51 info0 on CISA KEV0ATT&CK
Showing 65 of 65 findings

Findings

  • Detected generic-api-key: Detected a Generic API Key, potentially exposing access to various services and sensitive operations
    Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    gitleaks
  • Detected generic-api-key: Detected a Generic API Key, potentially exposing access to various services and sensitive operations
    Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    gitleaks
  • Detected generic-api-key: Detected a Generic API Key, potentially exposing access to various services and sensitive operations
    Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    gitleaks
  • Detected generic-api-key: Detected a Generic API Key, potentially exposing access to various services and sensitive operations
    Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    gitleaks
  • Detected generic-api-key: Detected a Generic API Key, potentially exposing access to various services and sensitive operations
    Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    gitleaks
  • SQL built by concatenation/Sprintf passed to Query/Exec/QueryRow — SQL injection. The statement text is assembled from a formatted or concatenated string (directly or via an intermediate variable). Us
    SQL built by concatenation/Sprintf passed to Query/Exec/QueryRow — SQL injection. The statement text is assembled from a formatted or concatenated string (directly or via an intermediate variable). Use parameterized placeholders ($1/?) with separate args, never string building. C…
    semgrep_example/trace/main.go:194
  • Image user should not be 'root'
    Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.
    trivy_example/simple/Dockerfile:0
  • Ensure that a user for the container has been created
    Ensure that a user for the container has been created on /_example/simple/Dockerfile.
    checkov_example/simple/Dockerfile:1
  • Ensure that HEALTHCHECK instructions have been added to container images
    Ensure that HEALTHCHECK instructions have been added to container images on /_example/simple/Dockerfile.
    checkov_example/simple/Dockerfile:1
  • Ensure top-level permissions are not set to write-all
    Ensure top-level permissions are not set to write-all on on(Go)
    checkov.github/workflows/go.yaml:0
  • Ensure top-level permissions are not set to write-all
    Ensure top-level permissions are not set to write-all on on(CIFuzz)
    checkov.github/workflows/cifuzz.yaml:0
  • Ensure top-level permissions are not set to write-all
    Ensure top-level permissions are not set to write-all on on(dockerfile)
    checkov.github/workflows/docker.yaml:0
  • 'RUN cd ...' to change directory
    Use WORKDIR instead of proliferating instructions like 'RUN cd … && do-something', which are hard to read, troubleshoot, and maintain.
    trivy_example/simple/Dockerfile:28

This report is public.