coreyhaines31/marketingskills conversion-tracking
Checked the catalogued skill at conversion-tracking.
D set by findings not listed
D set by findings not listed
B; retained sample includes a medium finding · SD-007 · what this rule accepts as a false positive →
21 suppressed by AI triage
The file is documentation and the outbound call is an example, not executable code.
The file is documentation and the outbound call is an example, not executable code.
The file is documentation and the outbound call is an example, not executable code.
The file is documentation and the outbound call is an example, not executable code.
The file is documentation and the outbound call is an example, not executable code.
The matched text appears to be a documentation note, not executable code or data exfiltration activity.
Legitimate outbound call to Acuity's conversion tracking domain, part of normal booking form integration
The code merely references a trusted external calendar iframe, not executing arbitrary network requests.
Same as above; this is a normal embed reference to a trusted domain.
The outbound reference is part of a legitimate embed script, not malicious.
Same reasoning; this is a benign external iframe source.
This is a standard Calendly embed script that only references an external host for a widget, not a malicious outbound call.
This is a standard Calendly embed script that only references an external host for a widget, not a malicious outbound call.
The code only constructs a URL string for matching iframe selectors; it does not perform an outbound request or grant network permissions, so it is not a real threat.
No actual path traversal string appears in the provided context; likely a false positive.
Empty lines only; scanner false positive.
The file contains no actual path traversal patterns, just empty lines; likely a false positive.
The file is documentation; the detected pattern likely appears in comments or examples, not as executable code, so it poses no threat.
Documentation file contains illustrative text, not executable code, so path traversal references are benign examples.
No path traversal evidence in the context; the line contains only empty content.
The reference to "[REDACTED]" is part of documentation describing a relative path used in a configuration file; it does not represent executable code that could exploit path traversal.