When running dependency-check I get the following error:
[ERROR] The disableNSP argument has been deprecated and replaced by disableNodeAudit
[ERROR] The disableNSP argument will be removed in the next version
We don't supply this argument through the command-line arguments:
$ dependency-check -s . --enableExperimental -f JSON -f HTML --suppression dependency-suppression.xsd --exclude "**/docs/**" --exclude "Danger/" --propertyfile "dependencycheck.properties" --connectiontimeout 60000 --ossIndexUsername $SONATYPE_USERNAME --ossIndexPassword $SONATYPE_PASSWORD --ossIndexRemoteErrorWarnOnly true --bundleAuditWorkingDirectory .
Our properties file supplies analyzer.node.audit.enabled=false, which I believe is the right value.
# defines if the experimental and retired analyzers can be enabled
analyzer.experimental.enabled=true
analyzer.retired.enabled=false
# ios specific
analyzer.cocoapods.enabled=true
analyzer.ruby.gemspec.enabled=true
analyzer.swift.package.manager.enabled=true
analyzer.swift.package.resolved.enabled=true
# others
analyzer.archive.enabled=true
analyzer.assembly.enabled=false
analyzer.autoconf.enabled=false
analyzer.bundle.audit.enabled=true
analyzer.cmake.enabled=false
analyzer.composer.lock.enabled=false
analyzer.cpanfile.enabled=false
analyzer.golang.dep.enabled=false
analyzer.golang.mod.enabled=false
analyzer.jar.enabled=false
analyzer.node.audit.enabled=false
analyzer.node.package.enabled=false
analyzer.nugetconf.enabled=false
analyzer.nuspec.enabled=false
analyzer.openssl.enabled=false
analyzer.pe.enabled=false
analyzer.pip.enabled=false
analyzer.pipfile.enabled=false
analyzer.pnpm.audit.enabled=false
analyzer.python.distribution.enabled=false
analyzer.python.package.enabled=false
analyzer.retirejs.enabled=false
analyzer.yarn.audit.enabled=false
Is this a bug, or an issue with our configuration?
When running
dependency-checkI get the following error:We don't supply this argument through the command-line arguments:
Our properties file supplies
analyzer.node.audit.enabled=false, which I believe is the right value.Is this a bug, or an issue with our configuration?