You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2023. It is now read-only.
Feature Request
I have a VirusTotal package that I am working on. Its starting out with moodle and wordpress. I intend to expand outside of frameworks and into CMS.
Cross compatibility w/ VirusTotal clients and Malice.
Remain consistent with the header and JSON structure in the VirusTotal API's so the clients can have cross-compatibility.
Describe alternatives you've considered
Create unique identifiers if the data structure does have to differ so that VirusTotal clients can identify a Malice server and adjust w/ the way that the algorithm is processed.
Additional context
I have a GitHub for a moodle/virustotal client underway; if you got a malice server, then when the time comes, I would love to tinker around with that and expand the client to both VirusTotal and Malice.
The text was updated successfully, but these errors were encountered:
Feature Request
I have a VirusTotal package that I am working on. Its starting out with moodle and wordpress. I intend to expand outside of frameworks and into CMS.
Cross compatibility w/ VirusTotal clients and Malice.
Remain consistent with the header and JSON structure in the VirusTotal API's so the clients can have cross-compatibility.
Describe alternatives you've considered
Create unique identifiers if the data structure does have to differ so that VirusTotal clients can identify a Malice server and adjust w/ the way that the algorithm is processed.
Additional context
I have a GitHub for a moodle/virustotal client underway; if you got a malice server, then when the time comes, I would love to tinker around with that and expand the client to both VirusTotal and Malice.
The text was updated successfully, but these errors were encountered: