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 [email protected] 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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...