dashboard

Get Security Findings

Changed on

Security findings from the indexer's regex scan.

Read-on-demand from security_findings.json per the α decision (no security_findings table on the hosted side). Ordered source → test → docs, then high → med → low severity, then file path, line and id, so the UI ordering is stable across calls. Returns an empty payload for snapshots indexed before 3C-bis.

get/snapshots/{snapshot_id}/security-findings

Request

  • Base URL
    https://api.repowise.dev (the document declares no server; this is the origin it was published from)
  • URL
    https://api.repowise.dev/snapshots/{snapshot_id}/security-findings
  • Auth
    HTTP bearer

Path parameters

snapshot_idstring required

Query parameters

severitystring nullable

Filter by severity: 'high' | 'med' | 'low'

file_pathstring nullable

Filter to a single file path

scope'source' | 'test' | 'docs' | 'all'

Filter by where the file sits: 'source' | 'test' | 'docs' | 'all'

limitinteger

Response

Successful Response

totalinteger
class_countsobject

Changes

  • 29a9df53f763Revision changes
    • info

      added the new optional query request parameter scope

    • info

      added the optional property to the response with the status

    • info

      added the optional property // to the response with the status