Did you just download a file that has been digitally signed by Json.NET (.NET Foundation) and wonder if the file is safe? If that's the case, please read on.
You will probably see Json.NET (.NET Foundation) when clicking to run the file. The publisher name is displayed as the "Verified publisher" in the UAC dialog as the screencap shows:
You can view the additional details from the Json.NET (.NET Foundation) digital signature with the following steps:
Here's a screenshot of a file that has been signed by Json.NET (.NET Foundation):
As you can see in the screenshot above, Windows states that "This digital signature is OK". This implies that the file has been published by Json.NET (.NET Foundation) and that the file has not been tampered with.
If you click the View Certificate button shown in the screengrab above, you can view all the details of the certificate, such as when it was issued, who issued the certificate, how long it is valid, etc. You can also see the address for Json.NET (.NET Foundation), such as the street name, city and country.
.NET Foundation Projects Code Signing CA has issued the Json.NET (.NET Foundation) certificates. You can also view the details of the issuer by clicking the View Certificate button shown in the screenshot above.
The following are the Json.NET (.NET Foundation) files I have collected, thanks to the FreeFixer users.
Detection Ratio | File Name |
---|---|
0/67 | Newtonsoft.Json.dll |
0/65 | Newtonsoft.Json.dll |
0/69 | Newtonsoft.Json.dll |
The detection percentage is based on that I have gathered 201 scan reports for the Json.NET (.NET Foundation) files. 0 of these scan results came up with some sort of detection. If you like, you can view the full details of the scan results by examining the files listed above.
The analysis is done on certificates with the following serial numbers: