Splunk Dev

check_for_vulnerable_javascript_library_usage Failure in Add-on created using Add-on Builder 4.1.3

nithesh
Engager

Created a fresh Add-on using Splunk add-on builder v4.1.3 and getting check_for_vulnerable_javascript_library_usage failures in AppInspect.
Tried this suggestion https://community.splunk.com/t5/Building-for-the-Splunk-Platform/How-to-update-a-Splunk-Add-on-Build... export, delete, import and generated add-on multiple times but still the issue persists.
Please suggest a fix for this issue. Thanks.

 

Screenshot 2023-10-10 at 6.33.16 PM.png

 

Labels (2)
0 Karma

thellmann
Splunk Employee
Splunk Employee

Hi @nithesh - since your original post, we've released updates to the Splunk AppInspect API that refined the behavior of this check. If you are still having issues, please reach out to appinspect@splunk.com and we'll help investigate. 

0 Karma

nithesh
Engager

Fixed this issue by doing a clean installation of the spunk addon builder (by manually deleting the directory and installing it again).

0 Karma
Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...