According to ETSI GS NFV-SOL 004 V2.7.1 (2019-12) https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/004/02.07.01_60/gs_NFV-SOL004v020701p.pdf

Chapter 4.3.2 VNF package manifest file

"The manifest file shall include a list of all files contained in or referenced from the VNF package with their location, expressed using a Source: location/name key-value pair. The manifest file itself may be included in the list. "

VNFSDK validation rules doesn't check if all artifacts in csar package are listed in csar manifest file.

Currently VNFSDK checks only presence of files listed in manifest file as a "Source:" in csar archive, not vice versa, if all files from csar are listed as a "Source:" in manifest file.

This cause situation that successfully validated csar package using VNFSDK fails during SDC Onboarding (VSP software inport) because SDC mechanism implements this rule.