warning NU1905: Audit source 'fix11-local-audit' did not provide any vulnerability
data. names the source under <auditSources> in your
nuget.config that gave the restore no vulnerability data. In this test that
source was an empty local folder. Point <auditSources> at a source that
publishes the data, such as nuget.org.
With nuget.org in its place the same restore printed no warning.
Aud1, auditfeed and fix11-local-audit are this test's
own names. The commands on this page ran in cmd.
The error
dotnet restore --force
Determining projects to restore...
C:\...\cfg\Aud1\Aud1.csproj : warning NU1905: Audit source 'fix11-local-audit' did not provide any vulnerability data.
Restored C:\...\cfg\Aud1\Aud1.csproj (in 48 ms).
exit=0
The project path is shortened; nothing else changed. It is a warning: the restore finished with exit code 0, and the package was restored.
Why it happens
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<clear />
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
</packageSources>
<auditSources>
<clear />
<add key="fix11-local-audit" value="auditfeed" />
</auditSources>
</configuration>
auditfeed is an empty folder inside the project folder; it held no packages
and no files of any kind. The warning named that source, by its key, and not nuget.org,
which was the package source in the same file. For a source that cannot be reached at
all, see NU1900.
The fix
...
<auditSources>
<clear />
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
</auditSources>
</configuration>
dotnet restore --force
Determining projects to restore...
Restored C:\...\cfg\Aud1\Aud1.csproj (in 3.79 sec).
exit=0
The two runs printed this much: the first, with the empty folder, the NU1905 warning and
a restore in 48 ms; the second, with nuget.org as the audit source, no warning and a
restore in 3.79 seconds. Silencing the warning with NoWarn would have hidden
the first result without changing it, so fix the source instead.
Only <auditSources> changed between the runs; the package source was
nuget.org in both. A setup with packages from a private feed and nuget.org as the audit
source was not tested here.
How it was reproduced
A console project from dotnet new console -f net10.0 with SDK 11.0.100 on
Windows 11 and Newtonsoft.Json 13.0.4, already in the global packages
folder. A nuget.config in the project folder listed nuget.org as the package
source and an empty folder auditfeed as the only audit source.
dotnet restore --force ran once with that, and once with nuget.org as the
audit source.
Every command shown without a PS> marker ran in cmd: a PowerShell script passed it as cmd /c ... 2>&1 and printed the exit= line after it.
Frequently asked
- How do I fix NU1905 audit source did not provide any vulnerability data?
- Name a source that publishes vulnerability data under auditSources in nuget.config. In this test replacing an empty local folder with https://api.nuget.org/v3/index.json made the warning go away.
- Does NU1905 fail the restore?
- Not by itself. In this test the restore printed warning NU1905, restored the package and exited with code 0.
- What did the audit source hold when NU1905 appeared?
- In this test it was an empty folder inside the project folder, named under auditSources with the key fix11-local-audit. The warning named that key.
More decoded errors in the Fixes category. For a vulnerable package itself, see NU1903.