New Repository Finding
Data Element for a New Repository Finding
Overview
The tables below define the data elements available in the Workflow action for a New Repository Finding Detected trigger. Please note you will need to prepend all data elements with data. , example: data.finding.id
Finding
1880737
Unique identifier for the finding within Heeler
2172405
Identifier of the code root (module or artifact) where the finding was detected
CVE-2025-15284
Public vulnerability identifier associated with this finding
qs
Name of the vulnerable package or dependency
6.5.3
Version of the package that is vulnerable
HIGH
Normalized severity level of the finding
17445572
Internal reference ID linking to the vulnerability record
2026-01-06T20:08:05.041112
Timestamp when the finding was first created
2026-01-06T20:08:05.041113
Timestamp when the finding was last updated
2
The Heeler Risk:
null
Original risk score before adjustments or recalculation
3
Business impact score assigned to the finding
null
Optional tier or classification assigned to the finding
Unassigned
Highest impact deployment environment associated with the finding
null
Environment-specific impact score
true
Indicates whether the vulnerability is exploitable
null
Indicates if the resource affect is internet accessible
false
Indicates whether the finding has been mitigated
null
Indicates whether the finding was observed at runtime
null
Indicates evidence of active compromise
null
Indicates whether this finding can be chained with others
1
Threat impact score used in overall risk calculation
null
Evidence or details of a known exploit
11198269
Dependency version where the vulnerability was introduced
null
Dependency version where the vulnerability was fixed
null
Reason the finding was marked as fixed
null
Timestamp when the vulnerability was fixed
null
Commit or changeset that fixed the vulnerability
null
Committer responsible for the fix
null
Earliest deployment timestamp containing the fix
null
Latest deployment timestamp containing the fix
null
Timestamp when the finding was fully remediated
2026-02-27T23:15:42.703000
SLA/SLO due date for remediation
2026-02-27T23:15:42.703000
Original SLA/SLO due date before changes
null
Indicates whether the finding can be automatically fixed
null
Indicates whether the finding was automatically fixed
Dependency Version
11198269
Unique identifier for the dependency version
qs
Dependency name
6.5.3
Dependency version number
true
Indicates the dependency was detected in source code
false
Indicates the dependency was observed at runtime
2025-07-26T21:07:20
Timestamp when the dependency was introduced
56e0bd3597...
Commit that introduced the dependency
2025-07-26T21:07:20
First time the dependency was observed
2026-01-06T20:08:00.094144
Most recent observation of the dependency
2025-07-26T21:07:20
Last known observation timestamp
unknown
Indicates whether the dependency version is pinned
Resource (Repository)
1026889835
Internal identifier for the repository
acme
Organization that owns the repository
woocommerce
Repository name
acme/woocommerce
Fully qualified repository name
PHP
Primary programming language
main
Default branch of the repository
2025-07-26T20:47:01
Repository creation timestamp
2025-07-26T21:09:32
Last update timestamp
null
Indicates whether the repository is private
internal
Visibility level of the repository in Heeler
Vulnerability
17445572
Unique identifier for the vulnerability record
CVE-2025-15284
Public vulnerability identifier
qs: Denial of Service via improper input validation
Human-readable vulnerability title
Improper Input Validation vulnerability in qs...
Detailed description of the vulnerability
HIGH
Reported severity of the vulnerability
7.5
CVSS base score
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS vector string
0.00152
EPSS probability score
2025-12-29T23:15:42.703000
Public disclosure date
["CWE-20"]
Common Weakness Enumeration identifiers
["<6.14.1"]
Versions affected by the vulnerability
["6.14.1"]
Versions where the vulnerability is fixed
Code Root
2172405
Unique identifier for the code root
h4r>>github>>github_repository>>acme >>woocommerce
Repository identifier associated with the code root
pnpm-lock.yaml
File where the dependency was detected
npm
Package manager used
npm
Dependency ecosystem
2025-07-26T21:07:20
Commit timestamp for the code root
Last updated
Was this helpful?
